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 353760 - gnome_segv should not spawn bug-buddy if the crashing application is bug-buddy
gnome_segv should not spawn bug-buddy if the crashing application is bug-buddy
Status: RESOLVED FIXED
Product: libgnomeui
Classification: Deprecated
Component: general
2.15.x
Other All
: Normal normal
: future
Assigned To: libgnomeui maintainers
libgnomeui maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-31 23:20 UTC by Matthew Barnes
Modified: 2006-09-26 17:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Proposed patch (614 bytes, patch)
2006-08-31 23:35 UTC, Matthew Barnes 		none Details | Review

Description Matthew Barnes 2006-08-31 23:20:40 UTC 
Please describe the problem:
The gnome_segv program should check that the crashed application was not bug-buddy before spawning bug-buddy.  This can lead to an endless cycle of bug-buddy spawning bug-buddy.

Steps to reproduce:
1. $ export G_DEBUG=fatal_warnings
2. $ bug-buddy --package=gnome-terminal  (any package name will do)

Actual results:
At least with the version I'm running (2.15.92), bug-buddy will produce some spurious warning about not being able to load an icon.

The warning will cause bug-buddy to abort (due to the G_DEBUG setting), which will spawn bug-buddy, which will produce the same warning, which will cause bug-buddy to abort, which will spawn bug-buddy, and so on.

Expected results:
The gnome_segv program should give up if bug-buddy itself crashes.

Does this happen every time?
Yes

Other information:
Comment 1 Matthew Barnes 2006-08-31 23:35:52 UTC 
Created attachment 71998 [details] [review]
Proposed patch
Comment 2 Matthew Barnes 2006-09-26 17:10:29 UTC 
Committed this myself.