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 105636 - Crash while debugging gnome-theme-manager
Crash while debugging gnome-theme-manager
Status: RESOLVED DUPLICATE of bug 97756
Product: memprof
Classification: Other
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: MemProf Maintainers
MemProf Maintainers
: 106028 126670 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-09 14:17 UTC by kmaraas
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kmaraas 2003-02-09 14:12:49 UTC 
Package: memprof
Severity: normal
Version: GNOME2.2.0 0.5.1
os_details: Gnome.Org
Synopsis: Crash while debugging gnome-theme-manager
Bugzilla-Product: memprof
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
Can't say what exactly caused it. I *think* it happened just after
pressing the "Leaks" button.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/gnome/head/INSTALL/bin/memprof'

[New Thread 1024 (LWP 1531)]
0x409c0219 in __wait4 () at __wait4:-1
	in __wait4

+ Trace 33649

Thread 1 (Thread 1024 (LWP 1531))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 leak_block_select_row
    at main.c line 378
  • #7 _gtk_marshal_VOID__INT_INT_BOXED
    at gtkmarshalers.c line 1362
  • #8 g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #10 g_signal_emit_valist
    at gsignal.c line 2554
  • #11 gtk_signal_emit
    at gtksignal.c line 358
  • #12 gtk_clist_button_press
    at gtkclist.c line 5003
  • #13 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #14 g_type_class_meta_marshal
    at gclosure.c line 514
  • #15 g_closure_invoke
    at gclosure.c line 437
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #17 g_signal_emit_valist
    at gsignal.c line 2564
  • #18 g_signal_emit
    at gsignal.c line 2612
  • #19 gtk_widget_event_internal
    at gtkwidget.c line 3143
  • #20 gtk_propagate_event
    at gtkmain.c line 2253
  • #21 gtk_main_do_event
    at gtkmain.c line 1502
  • #22 gdk_event_dispatch
    at gdkevents-x11.c line 2018
  • #23 g_main_dispatch
    at gmain.c line 1653
  • #24 g_main_context_dispatch
    at gmain.c line 2197
  • #25 g_main_context_iterate
    at gmain.c line 2278
  • #26 g_main_loop_run
    at gmain.c line 2498
  • #27 gtk_main
    at gtkmain.c line 1092
  • #28 main
    at main.c line 1881
  • #29 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-09 09:12 -------

The original reporter (kmaraas@online.no) 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-02-12 18:16:05 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Marking priority->high & severity->critical (it's
a crasher), adding bugsquad keyword, and marking as new.
Comment 2 Elijah Newren 2003-02-13 22:20:42 UTC 
*** Bug 106028 has been marked as a duplicate of this bug. ***
Comment 3 Elijah Newren 2003-12-11 04:35:21 UTC 
*** Bug 126670 has been marked as a duplicate of this bug. ***
Comment 4 John Gardiner Myers 2004-09-11 00:36:33 UTC 

*** This bug has been marked as a duplicate of 97756 ***