search for: yyoverflow

...nt in `src/main/gram.c`: > > ``` > > /* Memory leak > > yyparse(), as generated by bison, allocates extra space for the parser > stack using malloc(). Unfortunately this means that there is a memory > leak in case of an R error (long-jump). In principle, we could define > yyoverflow() to relocate the parser stacks for bison and allocate say on > the R heap, but yyoverflow() is undocumented and somewhat complicated > (we would have to replicate some macros from the generated parser here). > The same problem exists at least in the Rd and LaTeX parsers in tools. > */...

Hi, The behavior of ``` SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); ``` defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending on the string to be parsed. Trying to parse a string such as `"list(''=1+"` sets the `ParseStatus` to incomplete parsing error but trying to parse `"list(''=123"` will result in R sending a message to the

...gt; /* Memory leak > >> > >> yyparse(), as generated by bison, allocates extra space for the parser > >> stack using malloc(). Unfortunately this means that there is a memory > >> leak in case of an R error (long-jump). In principle, we could define > >> yyoverflow() to relocate the parser stacks for bison and allocate say on > >> the R heap, but yyoverflow() is undocumented and somewhat complicated > >> (we would have to replicate some macros from the generated parser here). > >> The same problem exists at least in the Rd and LaTeX...

I found the following code comment in `src/main/gram.c`: ``` /* Memory leak yyparse(), as generated by bison, allocates extra space for the parser stack using malloc(). Unfortunately this means that there is a memory leak in case of an R error (long-jump). In principle, we could define yyoverflow() to relocate the parser stacks for bison and allocate say on the R heap, but yyoverflow() is undocumented and somewhat complicated (we would have to replicate some macros from the generated parser here). The same problem exists at least in the Rd and LaTeX parsers in tools. */ ``` Could this be...

...t;> ``` >> >> /* Memory leak >> >> yyparse(), as generated by bison, allocates extra space for the parser >> stack using malloc(). Unfortunately this means that there is a memory >> leak in case of an R error (long-jump). In principle, we could define >> yyoverflow() to relocate the parser stacks for bison and allocate say on >> the R heap, but yyoverflow() is undocumented and somewhat complicated >> (we would have to replicate some macros from the generated parser here). >> The same problem exists at least in the Rd and LaTeX parsers in too...

...>>> >> yyparse(), as generated by bison, allocates extra space for the parser >>> >> stack using malloc(). Unfortunately this means that there is a memory >>> >> leak in case of an R error (long-jump). In principle, we could define >>> >> yyoverflow() to relocate the parser stacks for bison and allocate say >>> on >>> >> the R heap, but yyoverflow() is undocumented and somewhat complicated >>> >> (we would have to replicate some macros from the generated parser >>> here). >>> >> Th...

...gt;> >> >> >> yyparse(), as generated by bison, allocates extra space for the parser >> >> stack using malloc(). Unfortunately this means that there is a memory >> >> leak in case of an R error (long-jump). In principle, we could define >> >> yyoverflow() to relocate the parser stacks for bison and allocate say >> on >> >> the R heap, but yyoverflow() is undocumented and somewhat complicated >> >> (we would have to replicate some macros from the generated parser >> here). >> >> The same problem exist...

...gt;> yyparse(), as generated by bison, allocates extra space for the > parser > >> stack using malloc(). Unfortunately this means that there is a > memory > >> leak in case of an R error (long-jump). In principle, we could > define > >> yyoverflow() to relocate the parser stacks for bison and > allocate say on > >> the R heap, but yyoverflow() is undocumented and somewhat > complicated > >> (we would have to replicate some macros from the generated > parser here). > >> The same prob...

...nerated by bison, allocates extra space for the > parser > >>>>>> stack using malloc(). Unfortunately this means that there is a > memory > >>>>>> leak in case of an R error (long-jump). In principle, we could > define > >>>>>> yyoverflow() to relocate the parser stacks for bison and allocate > say > >>>> on > >>>>>> the R heap, but yyoverflow() is undocumented and somewhat > complicated > >>>>>> (we would have to replicate some macros from the generated parser > >...

...tes extra space >> for the parser >> >> stack using malloc(). Unfortunately this means that there >> is a memory >> >> leak in case of an R error (long-jump). In principle, we >> could define >> >> yyoverflow() to relocate the parser stacks for bison and >> allocate say on >> >> the R heap, but yyoverflow() is undocumented and somewhat >> complicated >> >> (we would have to replicate some macros from the generated >> parse...

...;>>> yyparse(), as generated by bison, allocates extra space for the parser >>>>>> stack using malloc(). Unfortunately this means that there is a memory >>>>>> leak in case of an R error (long-jump). In principle, we could define >>>>>> yyoverflow() to relocate the parser stacks for bison and allocate say >>>> on >>>>>> the R heap, but yyoverflow() is undocumented and somewhat complicated >>>>>> (we would have to replicate some macros from the generated parser >>>> here). >>&g...