[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison 1.875 has memory corruption problems

From: Chris Lattner
Subject: Re: Bison 1.875 has memory corruption problems
Date: Mon, 5 Apr 2004 15:28:34 -0500 (CDT)

On Mon, 5 Apr 2004, Paul Eggert wrote:
> > when using the 'make maintainer-check-valgrind' target in the tests
> > directory....
> >
> >   1: input.at:28       FAILED near `input.at:37'
> >   2: input.at:46       FAILED near `input.at:55'
> >   ...
> This suggests some problem in invoking valgrind. Recent versions of
> valgrind have a different calling convention, and Bison hasn't been
> altered to accommodate them.  If you're using the maintainer rules,
> you'll need to adjust the valgrind invocations to match the versions of
> the tools that you're using.

I have observed the exact same problems running bison+valgrind on the
command line.  e.g.:

$ cd bison-1.875/tests/testsuite.dir/004
$ valgrind ../../../src/bison input.y
==17409== Conditional jump or move depends on uninitialised value(s)
==17409==    at 0x8057E6C: lloc_default (location.h:43)
==17409==    by 0x8056782: gram_parse (parse-gram.c:1246)
==17409==    by 0x805B6C2: reader (reader.c:501)
==17409==    by 0x804E37E: main (main.c:80)
==17409==    by 0x4026A54C: __libc_start_main (in /lib/libc-2.3.2.so)
==17409==    by 0x8049260: (within

This is when compiled with GCC 3.3, though I see even worse problems when
compiled with my compiler.  I believe the problem is due to an
uninitialized variable in the lexer somewhere.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]