On Sat, Nov 06, 2004 at 12:43:36PM -0500, Daniel Jacobowitz wrote: > "Invalid read" is not a memory leak - this says something has been > freed and then used. It looks like the destructors are running in the > wrong order, maybe. > > We'd still need a testcase.
A somewhat crappy testcase: $ apt-get install pari-gp $ valgrind gp \q ==30297== ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 33 from 1) If you run instead $ valgrind --run-libc-freeres=no gp \q ==30314== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 33 from 1) If you enter ^D instead of \q you do not get errors, so it might be linked to the libc I/O subsystem. (GP is a CLI using GNU readline.) Of course I did not rule out a bug in the gp binary itself, but I suppose the submitter observed the problem in an unrelated program. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]