|flex++ bison++ email@example.com (Antonio Bleile) (2001-08-06)|
|Re: flex++ bison++ firstname.lastname@example.org (Antonio Bleile) (2001-08-08)|
|From:||Antonio Bleile <email@example.com>|
|Date:||8 Aug 2001 01:10:38 -0400|
|Organization:||ask - Innovative =?iso-8859-1?Q?Visualisierungsl=F6sungen?= GmbH http: //www.askvisual.de & Technische Universitaet Darmstadt|
|Keywords:||lex, yacc, comment|
|Posted-Date:||08 Aug 2001 01:10:38 EDT|
Antonio Bleile schrieb:
> Has somebody experienced these problems? What am I doing wrong? Please
> note that this happens on an IRIX machine (O2, newest OS version...).
Ups, sorry, I didn't know that this group is moderated...
I found the bug. I did not initialize a pointer to NULL,
under IRIX you have to do it explicitely. But now I noticed
that I have a memory leak in the parser.... Maybe it's again
my code causing this. Do you know of memory leaks within
flex++, bison++ ?
[I don't know of any memory leaks in bison, but I do know that it's
easy for parse action code to forget to free dynamically allocated
strings or bits of parse tree. -John]
Return to the
Search the comp.compilers archives again.