> > There still are three of them in the library, but it's in the > > generated parser code. I just can't read this, so I will be unable > > to fix them. If anyone with more knowledge of bison/flex could > > tackle this, I'd of course help. > > Interesting. Did you use valgrind to find these? Yes I did. I also used it to locate and fix bad memory allocation/accessses in dmidecode (2.x) and associated tools. This is a really helpful tool and I'd recommend it to everyone. -- Jean Delvare http://www.ensicaen.ismra.fr/~delvare/
