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 700262 - Add a way to get backtraces from criticals and warnings
Add a way to get backtraces from criticals and warnings
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-13 22:10 UTC by Giovanni Campagna
Modified: 2013-05-14 21:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add a way to get backtraces from criticals and warnings (2.69 KB, patch)
2013-05-13 22:10 UTC, Giovanni Campagna 		committed Details | Review

Description Giovanni Campagna 2013-05-13 22:10:40 UTC 
Attaching gdb and running with G_DEBUG=fatal-warnings is not a very
fast to debug a specific issue (especially if you have warnings at
startup, since then you need to run the shell from a terminal).
Instead, introduce a new SHELL_DEBUG environment variable that can
be set to backtrace-warning, causing a gjs_dumpstack() after every
warning or critical.
Comment 1 Giovanni Campagna 2013-05-13 22:10:43 UTC 
Created attachment 244116 [details] [review]
Add a way to get backtraces from criticals and warnings
Comment 2 drago01 2013-05-14 20:55:31 UTC 
Review of attachment 244116 [details] [review]:

Makes sense is indeed more convenient.
Comment 3 Giovanni Campagna 2013-05-14 21:26:23 UTC 
Attachment 244116 [details] pushed as 12ba2b2 - Add a way to get backtraces from criticals and warnings