Thank you very much for your efforts. You helped me a lot.
> However, the gcc 3.x builds did trigger lots of valgrind errors (over
> ten million!); so there's definitely serious problems with the code
> (just nothing that causes a fatal crash).
I knew about the errors but I didn't talk about it,
Jonas Stahl wrote:
>> Try running the application under valgrind or some other memory debugger.
>> If possible also try slightly different releases of gcc (4.1.1 or 4.2);
>> there's an outside chance that it's a bug in gcc.
>
> Thanks. I think this isolated the fault a bit more.
> I tried debuggin
El jue, 15-11-2007 a las 21:30 +0100, [EMAIL PROTECTED] escribió:
> I will stick my neck out and say `YYLEX' is a macro, because I think I
> was
> overly cautious before. I don't know anything else it could be.
> (Just my
> opinion, but I loathe the term "method". Why they had to invent a new
>
>> Try running the application under valgrind or some other memory
>> debugger.
>> If possible also try slightly different releases of gcc (4.1.1 or 4.2);
>> there's an outside chance that it's a bug in gcc.
>
> Thanks. I think this isolated the fault a bit more.
> I tried debugging under valgrind.
> Try running the application under valgrind or some other memory debugger.
> If possible also try slightly different releases of gcc (4.1.1 or 4.2);
> there's an outside chance that it's a bug in gcc.
Thanks. I think this isolated the fault a bit more.
I tried debugging under valgrind. The result
Jonas Stahl wrote:
> In the version with segmentation fault (gcc 4.1.2):
>
> 33117 if (yychar == YYEMPTY)
> (gdb)
> 33120 yychar = YYLEX;
> (gdb)
>
> Program received signal SIGSEGV, Segmentation fault.
> yyparse () at fullParser.tab.c:33120
> 33120 yychar = YYLEX;
>
>
> I
> The result of debugging in short:
> In the version with segmentation fault (gcc 4.1.2):
>
> 33117 if (yychar == YYEMPTY)
> (gdb)
> 33120 yychar = YYLEX;
> (gdb)
>
> Program received signal SIGSEGV, Segmentation fault.
> yyparse () at fullParser.tab.c:33120
> 33120 yychar = YYL
> Well, is the use of bison/flex required? My initial reaction when I saw
> the code was "Why the hell is he writing a parser for a very specific
> XML file format with bison/flex?". Unless the use of bison/flex is
> required, I would strongly recommend using libxml2 to parse the XML
> (heck, given
Ok, first thanks for the replies. I already debugged it with gdb before
writing to the mailing list. Cause I'm not very used to debugging C Code it
didn't help me very much.
The result of debugging in short:
The debugger jumps from main() to yyparse() and the error occurs at the
first time the c
Jonas Stahl wrote:
> Hi,
>
> I'm a german student (so sorry for my bad english).
>
> I'm working at my bachelor thesis and I'm having a little problem with
> Bison/Flex.
> [snip]
> Does Anybody have a good hint for me?
Well, is the use of bison/flex required? My initial reaction when I saw
the c
> I'm a german student (so sorry for my bad english).
It doesn't seem that bad to me, but if you have trouble with anything,
just write in German. I understand it and I think some other people here
do, too.
> I'm using a Bison/Flex application, that was written by another student
> for
> his bac
El mar, 13-11-2007 a las 17:07 +0100, Jonas Stahl escribió:
>
> yychar = YYLEX; <---
Most likely a bug in your yylex () implementation. You should debug it
there.
Claudio
--
Claudio Saavedra <[EMAIL PROTECTED]>
___
help-bison@gnu.org http://l
12 matches
Mail list logo
