2c2479581a
After we receive one of the tracked signals, in case we get stuck inside the gjs_dumpstack () call, we use an alarm to raise the previously emitted signal, however without using SA_NODEFER, the raise inside the alarm handler will be ignored. To avoid to handle new signals caused by the handler calls, once we get the first signal, we just ignore them all as they could only lead to dirty traces. Also, cleaning up a bit the code, and disabling the shell log handler in dump_gjs_stack_alarm_sigaction since this might lead to a new gjs_dumpstack () request. https://bugzilla.gnome.org/show_bug.cgi?id=789237
GNOME Shell provides core user interface functions for the GNOME 3 desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience. For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see: https://wiki.gnome.org/Projects/GnomeShell Bugs should be reported at http://bugzilla.gnome.org against the 'gnome-shell' product. License ======= GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.