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 388441 - create minidump files for crashes
create minidump files for crashes
Product: bug-buddy
Classification: Deprecated
Component: general
Other Linux
: High critical
: ---
Assigned To: Fernando Herrera
libgnomeui maintainers
Depends on:
Blocks: 436832 447852
Reported: 2006-12-21 23:10 UTC by Fernando Herrera
Modified: 2008-08-31 21:38 UTC
See Also:
GNOME target: 2.24.x
GNOME version: 2.17/2.18

gnome airbag C wrapper, 1st version (39.94 KB, application/x-gzip)
2006-12-21 23:12 UTC, Fernando Herrera
Patch for libgnomeui to use gnome-airbag wrapper, 1st version (5.13 KB, patch)
2006-12-21 23:13 UTC, Fernando Herrera
none Details | Review
support for the new directory in bug-buddy (1.70 KB, patch)
2006-12-22 01:37 UTC, Fernando Herrera
none Details | Review GTK_MODULE implementation (44.70 KB, application/x-gzip)
2006-12-22 01:40 UTC, Fernando Herrera

Description Fernando Herrera 2006-12-21 23:10:15 UTC
If there is no gdb installed on the system, or the crashing program has not debug symbols, then libgnomeui should dump a minidump file and invoke bug-buddy with that file, so bug-buddy can send it to the debugserver, enrich it with a nice stacktrace and send it back to bugzilla.
Comment 1 Fernando Herrera 2006-12-21 23:12:24 UTC
Created attachment 78764 [details]
gnome airbag C wrapper, 1st version

Notice that google's airbag linux support has not yet landed, so you need to manually apply last patch in issue 100:
Comment 2 Fernando Herrera 2006-12-21 23:13:07 UTC
Created attachment 78765 [details] [review]
Patch for libgnomeui to use gnome-airbag wrapper, 1st version
Comment 3 Fernando Herrera 2006-12-21 23:22:36 UTC
humm, maybe we could implement this as a GTK_MODULE instead...
Comment 4 Fernando Herrera 2006-12-22 00:29:46 UTC
Ok, much cleaner the GTK_MODULES approarch, and then libgnomeui is not depending on libstdc++/airbag.

Now bug-buddy can itself install the .so file to be loaded though gnome-session
Patch coming.
Comment 5 Fernando Herrera 2006-12-22 01:37:13 UTC
Created attachment 78767 [details] [review]
support for the new directory in bug-buddy
Comment 6 Fernando Herrera 2006-12-22 01:40:20 UTC
Created attachment 78769 [details] GTK_MODULE implementation

This module install an airbag seghandler.
When something crashes it does:
 - Release keyboard/display grabs
 - If GNOME_HACKER and gdb --> run gnome-terminal with gdb and finish
 - If gdb && bug-buddy && debug_symbols --> run bug-buddy in the old (gdb) way
 - If none of above --> dump a minidump file

TODO: invoke bug-buddy with the minidump file
Comment 7 Fernando Herrera 2006-12-27 00:01:39 UTC
After some comments from Olav and jrb we should not rely on gnome-session to set up the env variable GTK_MODULES. A better approach would be to hack gtk+ to support some special dirs containing modules that should be always loaded.
Comment 8 Alexander “weej” Jones 2006-12-30 01:49:34 UTC
People are getting annoyed with the number of crash reports on Bugzilla, with many simply ignoring it in favour of mailing lists due to the sheer volume of noise.

I think maybe crash reports should be directed elsewhere and "promoted" to bugzilla by some other means.

This way, outdated software can continue to crash and be logged on the crash server, long after the bug is fixed. Perhaps we could reject the report if the user's software is so old it is unsupported, and the client software can report back to the user that this is the case.

Pie in the sky.
Comment 9 Ross Burton 2007-07-04 06:33:13 UTC
Quoting Mattias:

Whats the problem with using the Gtk/Modules XSetting that was invented
especially for this purpose ?

Can we apply this or #449733?
Comment 10 Fernando Herrera 2007-08-28 00:50:28 UTC
Done ;)
Comment 11 André Klapper 2008-06-09 16:48:07 UTC
OK. So we have a mostly useless installation that is already in use and receives hundreds of bug reports, and nobody gives a fuck because it is mainly unusable, missing debug info for nearly every distribution, more or less unmaintained, and deployed in an untested state.
I've at least ask for documentation a few times before GNOME 2.22.0 was released, and nothing has happened.

Now either tell me how to switch off that feature in bug-buddy so we don't lose even more user information, or properly define a process how distros can submit debug info into the system and how to properly identify and check for major issues for showstopper reports.
Having two systems in parallel is just crap from a QA/controlling POV.

Comment 12 Cosimo Cecchi 2008-08-31 21:38:00 UTC
No reason for this to stay opened.