similar to: [PATCH] builder: better handle some index parsing errors

Switch the lex/yacc parser into reentrant mode, to ease the handling of parsing-specific data; introduce a new parser_context struct for that, which is added as extra data to the parser. This should cause no behaviour changes in the parsing, just no more global variables used for getting data in/out the parser. --- builder/index-parse.y | 44 ++++++++++++++++++++++++++++++++++++------

--- builder/index-parse.y | 6 ++++-- builder/index-parser-c.c | 3 ++- builder/index-struct.h | 1 + builder/ini_reader.ml | 6 +++--- builder/ini_reader.mli | 2 +- 5 files changed, 11 insertions(+), 7 deletions(-) diff --git a/builder/index-parse.y b/builder/index-parse.y index 310870d..7ddef53 100644 --- a/builder/index-parse.y +++ b/builder/index-parse.y @@ -150,12 +150,14 @@

Hi, this series introduces a basic support for registering/attaching/unregistering RHEL guests using subscription-manager, so it is possible to do for example: $ cat <<EOF > sm.conf [general] username=user password=pass [attach-0] pool=ID EOF $ virt-customize -a rhel-guest.qcow2 \ --sm-config sm.conf --sm-register --sm-attach 0 \ --install pkg1 --install pkg2

It looks like flex 2.6.1 changed [1] the return code for EOF in yyinput. Therefore, use the right value depending on the version of flex which generates the lexer. [1] https://github.com/westes/flex/commit/f863c9490e6912ffcaeb12965fb3a567a10745ff --- builder/index-scan.l | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/builder/index-scan.l b/builder/index-scan.l

On 2015-12-18 02:29, Simon Urbanek wrote: > Michael, > > I got access to PDP AIX so I can try to replicate your problem. Can you, please, share exactly your setup - AIX version and well as how exactly you installed the compilers (=where from)? I can then try to replicate it. AFAICS there is no official binary for gfortran nor gcc 4.7 so it must be some 3rd party - which could also be a

Always close the file (ignoring its result) after a parsing, and cleanup the parse_context object before any exit(). This eases the debugging of memory issues in the actual parser. --- builder/index-validate.c | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/builder/index-validate.c b/builder/index-validate.c index 4b7fe93..fed0f81 100644 ---

I have left this a few days but I still can't compile ael_lex.c in HEAD on CENTOS. I've installed ncurses and bison but I get the following error gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -O6 -march=i686 -fomit-frame-pointer -include ../include/ clude -I.. -fPIC -I. -c -o ael/aelflex.o ael/ael_lex.c In file included from

GCC has two warnings related to large stack frames. We were already using the -Wframe-larger-than warning, but this reduces the threshold from 10000 to 5000 bytes. However that warning only covers the static part of frames (not alloca). So this change also enables -Wstack-usage=10000 which covers both the static and dynamic usage (alloca and variable length arrays). Multiple changes are made

I finally succeded in compiling TableGen with Visual Studio. In the end I made normal solution and project files for VS instead of using Paolo's SConstruct based build system because of my lacking familiarity with SConstruct. One of the main obstacles was getting the FileLexer and FileParser to build correctly. First of all the output file for FileLexer is specified with a %option, which

So i am getting this cc1: warning: -Wformat-nonliteral ignored without -Wformat [-Wformat-nonliteral] libxlu_cfg_y.c: In function ''xlu__cfg_yyparse'': libxlu_cfg_y.c:1292:41: error: ''scanner'' undeclared (first use in this function) yychar = yylex (&yylval, &yylloc, scanner); ^ libxlu_cfg_y.c:1292:41: note:

Hi, from time to time, there have been requests (or attempts, like the mingw port posted on the list some months ago) to make libguestfs work on OSes different than Linux. Of course this would imply using a fixed appliance, since it is currently heavily dependent on Linux. The attached series provides some easy changes in this direction, resolving some of the easy issues found in porting to

On Thursday 20 March 2014 14:15:29 Richard W.M. Jones wrote: > On Thu, Mar 20, 2014 at 02:48:11PM +0100, Pino Toscano wrote: > > Always close the file (ignoring its result) after a parsing, and > > cleanup the parse_context object before any exit(). > > > > This eases the debugging of memory issues in the actual parser. > > --- > > > >

Ok, here is the patch again... I also included fixes for the bits that originally gave my mailer fits... Two votes for orange, so I went with orange... Doing diffs in .: --- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800 +++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800 @@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char * Result +=

--- builder/index-scan.l | 5 +++-- builder/test-virt-index-validate-good-4 | 3 +++ builder/test-virt-index-validate.sh | 1 + 3 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 builder/test-virt-index-validate-good-4 diff --git a/builder/index-scan.l b/builder/index-scan.l index bdb474b33..49dad72bc 100644 --- a/builder/index-scan.l +++

Introduced in 5cbdf35d651b6c730d62d9af4876039faa122efc, it caused the first character of the value to be skipped if the key has a subkey. --- builder/index-scan.l | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builder/index-scan.l b/builder/index-scan.l index 7a9618f..e43f82e 100644 --- a/builder/index-scan.l +++ b/builder/index-scan.l @@ -65,7 +65,7 @@ extern void yyerror

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 30 Aug 2004 21:46:42 -0700 >FileParser.tab.c: In function `int Fileparse()': >FileParser.tab.c:2043: error: syntax error before `goto' > >The offending lines bison generated are: > >/*----------------------------------------------------. >| yyerrlab1 -- error raised explicitly by an action. |

I've some code to manipulate incoming Caller-ID - so its suitable for replying to... [sipdef] exten => s,1,NoOp(FWD SIP: "${CALLERIDNAME}" <${CALLERIDNUM}>) ; Alter incoming calles from pulver - add a '87' exten => s,2,Gotoif($[${CALLERIDNAME} = ${CALLERIDNUM}]?3:4) exten => s,3,SetCIDName(87${CALLERIDNUM}) exten => s,4,SetCIDNum(87${CALLERIDNUM}) exten

Hello, [I'm redirecting this here from stats-rosuda-devel] When parsing R code through R_parseVector and the code generates an error (syntax error), is there a way to grab the error. It looks like yyerror populates the buffer "R_ParseErrorMsg", but then the variable is not part of the public api. Would it be possible to add yet another entry point to the parser that would

During our last week of Ferret / aaf usage (also our first week of Ferret / aaf usage), I have received 8 messages stating that our app encountered a Ferret::QueryParser::QueryParseException. For instance: A Ferret::QueryParser::QueryParseException occurred in foo#search: Error occurred in src/q_parser.y:279 - yyerror couldn''t parse query "com -- 404". Error message

On Mon, 30 Aug 2004 21:27:26 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > On Mon, 30 Aug 2004 20:48:45 -0700 > Jeff Cohen <jeffc at jolt-lang.org> wrote: > > > When I ran configure after updating, I get various errors. First: > > > > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc > > checking for a