Displaying 6 results from an estimated 6 matches for "yytname".
Did you mean:
myname
2024 May 28
1
Segfault when parsing UTF-8 text with srcrefs
...literals and comments, plus a missing bounds check. The "correct"
result should be an R error, which I get in a debug build.
The tokenizer ends up with a negative token and then when the parse data
are being finalized, creating a table of token names, there is an out of
bounds access (yytname array). Probably the check should go right away
into the tokenizer.
Tomas
>
> Hadley
>
2024 May 30
1
[External] Re: Segfault when parsing UTF-8 text with srcrefs
..., plus a missing bounds check. The "correct"
> result should be an R error, which I get in a debug build.
>
> The tokenizer ends up with a negative token and then when the parse data
> are being finalized, creating a table of token names, there is an out of
> bounds access (yytname array). Probably the check should go right away
> into the tokenizer.
>
> Tomas
>
> >
> > Hadley
> >
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
[[alternat...
2024 May 28
2
Segfault when parsing UTF-8 text with srcrefs
Hi all,
When I run the following code, R segfaults:
text <- "?"
srcfile <- srcfilecopy("test.r", text)
parse(textConnection(text), srcfile = srcfile)
It doesn't segfault if text is ASCII, or it's not wrapped in
textConnection, or srcfile isn't set.
Hadley
--
http://hadley.nz
[[alternative HTML version deleted]]
2012 Sep 11
4
[PATCH] libxl: Tolerate xl config files missing trailing newline
...6, 68, 69, 71, 73
+ 0, 47, 47, 48, 50, 51, 53, 54, 55, 57,
+ 59, 60, 62, 63, 65, 66, 68, 69, 70, 72,
+ 73, 75, 77
};
#endif
@@ -459,8 +461,8 @@ static const yytype_uint8 yyrline[] =
static const char *const yytname[] =
{
"$end", "error", "$undefined", "IDENT", "STRING", "NUMBER", "NEWLINE",
- "''=''", "'';''", "''[''", "'']''", "...
2006 Aug 15
2
Windows build with Visual Studio 2005 - some success
...= 259,
LOW = 260,
OR = 261,
@@ -67,7 +67,7 @@
};
#endif
/* Tokens. */
-#define WORD 258
+#define YYWORD 258
#define WILD_STR 259
#define LOW 260
#define OR 261
@@ -437,7 +437,7 @@
First, the terminals, then, starting at YYNTOKENS, nonterminals. */
static const char *const yytname[] =
{
- "$end", "error", "$undefined", "WORD", "WILD_STR", "LOW", "OR", "AND",
+ "$end", "error", "$undefined", "YYWORD", "WILD_STR", "LOW", "OR",...
2012 Aug 14
12
[TESTDAY] xl cpupool-create segfaults if given invalid configuration
# xl cpupool-create ''name="pool2" sched="credit2"''
command line:2: config parsing error near `sched'': syntax error,
unexpected IDENT, expecting NEWLINE or '';''
Failed to parse config file: Invalid argument
*** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 ***
Segmentation fault (core dumped)
Looking at the code