|
From: Julian S. <js...@ac...> - 2005-12-09 02:00:52
|
I looked briefly at this but got lost in the hash table stuff. I believe it may be some problem with freeing hash table components or some such in the wrong order, or at the wrong time. The bug has been there for a while, but only recently started producing segfaults, following a change in VG_(arena_free) to fill up freed memory with junk. J On Thursday 08 December 2005 20:53, Robert Walsh wrote: > > Recently I started getting a regression test error in > > memcheck/tests/mempool, the bottom line being "INTERNAL ERROR: Valgrind > > received a signal 11 (SIGSEGV) - exiting". > > Yup - I just noticed this yesterday. Hopefully I'll have some time > tomorrow or over the weekend to fix this up. > > Regards, > Robert. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |