Bison 1.35 memory leaks (valgrind report)

[Tim Van Holder]

Was trying out valgrind yesterday, and figured I'd run bison 1.35
through it as well (using a fairly large grammar).  The output is
attached.

There's a few invalid memory accesses that are a potential worry,
and several memory leaks (resulting in 4.6MB of 'lost memory' out
of a total allocation of 10MB).  The 'jump or move based on an
uninitialised value is probably harmless (although there's several
thousand of them due to the large grammar :-) ).
Granted, bison usually ends quickly and the memory will get
cleaned up at exit, but it still seems Wrong(tm).

valgrind.log
Description: Text document