Bug 84053 – Memprof crashed after clicking on the `leak' button

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 84053 - Memprof crashed after clicking on the `leak' button


Summary:	Memprof crashed after clicking on the `leak' button


Status:	RESOLVED INCOMPLETE

Product:	memprof
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Owen Taylor
QA Contact:	Owen Taylor

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-06-04 07:10 UTC by Hugues Talbot
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Hugues Talbot 2002-06-04 07:10:50 UTC

Package: memprof
Severity: major
Version: 0.4.1
Synopsis: Memprof crashed after clicking on the `leak' button
Bugzilla-Product: memprof
Bugzilla-Component: general

Description:
We'll you'd need my application, which I can't give you, sorry!


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 23274

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 strchr
from /lib/i686/libc.so.6
#5 ??
#6 _bfd_dwarf2_find_nearest_line
#7 _bfd_elf_find_nearest_line
#8 find_line
#9 leaks_print
#10 generate_leak_cb
#11 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#12 gtk_handlers_run
from /usr/lib/libgtk-1.2.so.0
#13 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#14 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#15 gtk_button_clicked
from /usr/lib/libgtk-1.2.so.0
#16 gtk_real_button_released
from /usr/lib/libgtk-1.2.so.0
#17 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#18 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#19 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#20 gtk_button_released
from /usr/lib/libgtk-1.2.so.0
#21 gtk_button_button_release
from /usr/lib/libgtk-1.2.so.0
#22 gtk_marshal_BOOL__POINTER
from /usr/lib/libgtk-1.2.so.0
#23 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#24 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#25 gtk_widget_event
from /usr/lib/libgtk-1.2.so.0
#26 gtk_propagate_event
from /usr/lib/libgtk-1.2.so.0
#27 gtk_main_do_event
from /usr/lib/libgtk-1.2.so.0
#28 gdk_event_dispatch
from /usr/lib/libgdk-1.2.so.0
#29 g_main_dispatch
from /usr/lib/libglib-1.2.so.0
#30 g_main_iterate
from /usr/lib/libglib-1.2.so.0
#31 g_main_run
from /usr/lib/libglib-1.2.so.0
#32 gtk_main
from /usr/lib/libgtk-1.2.so.0
#33 main
#34 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 strchr
from /lib/i686/libc.so.6
#5 ??
#6 _bfd_dwarf2_find_nearest_line
#7 _bfd_elf_find_nearest_line





------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-04 03:10 -------

The original reporter (hugues.talbot@csiro.au) 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, otaylor@redhat.com.

Comment 1 Ben FrantzDale 2002-08-01 01:09:49 UTC

This looks a lot like bug 67805, although the stack traces are
completely different.

Comment 2 Hugues Talbot 2002-08-01 02:12:13 UTC

Hi,

A recompilation of memprof with RH-7.3 current libraries solved that
problem. It looks like a compatibility issue.

Comment 3 Owen Taylor 2002-08-31 18:11:27 UTC

(I don't think it was actually the same as bug 67805... just
because they both happen when you click on leaks doesn't mean
they are the same.)

Too many variables here to make much out of at this point;
probably a binutils bug. If it is working for you now, good. :-)