After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 126670 - crashes when refering to non-existent memory leak
crashes when refering to non-existent memory leak
Status: RESOLVED DUPLICATE of bug 105636
Product: memprof
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: MemProf Maintainers
MemProf Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-10 22:15 UTC by dgarcia
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dgarcia 2003-11-10 23:29:43 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

Thread 1 (Thread 8192 (LWP 16516))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 leak_block_select_row
  • #7 _gtk_marshal_VOID__INT_INT_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_clist_button_press
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #23 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #29 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6




------- 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.

Comment 1 Elijah Newren 2003-12-11 04:35:23 UTC
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 ***