GNOME Bugzilla – Bug 126670
crashes when refering to non-existent memory leak
Last modified: 2004-12-22 21:47:04 UTC
Package: memprof Severity: normal Version: 0.5.0 Synopsis: crashes when refering to non-existent memory leak Bugzilla-Product: memprof Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: If you run the leak detector while the program is running you will get various entries in the leak table. The program is still running and some of those enties listed in the table will not be able to be found because the program has since allocated/deallocated various entries. When you click on one of the expired entries Memprof crashes instead of giving an error about the non-existent block. Steps to reproduce the problem: 1. Run a program that has a long run-time and alocates/deallocated lots of data. 2. Run a leak check while program is running. 3. Click on the leak results until you run into one that no longer exists. Actual Results: Crash Expected Results: Error Message How often does this happen? It is very reproduceable Additional Information: version 0.5 Debugging Information: Backtrace was generated from '/usr/bin/memprof' (no debugging symbols found)...[New Thread 8192 (LWP 16516)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 41626
Thread 1 (Thread 8192 (LWP 16516))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-10 18:29 ------- The original reporter (dgarcia@tx.aacisd.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, memprof-maint@bugzilla.gnome.org.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 105636 ***