gmessages: Clarify documentation about aborting on fatal log levelsa0456f9c96e8b31e352f124f5f7bdd9dfb3c8b8e254/head
commita0456f9c96e8b31e352f124f5f7bdd9dfb3c8b8e
authorPhilip Withnall <withnall@endlessm.com>
Mon, 20 Aug 2018 22:41:53 +0000 (20 23:41 +0100)
committerPhilip Withnall <withnall@endlessm.com>
Wed, 22 Aug 2018 09:37:15 +0000 (22 10:37 +0100)
treefb61b89805ac262122053b4f90fe56e75ccdd144
parentf6703db37817da99a9b734dc3d33086a57f54274
gmessages: Clarify documentation about aborting on fatal log levels

Clarify that we actually raise SIGTRAP rather than calling abort(). We
haven’t called abort() since about 2011, when commit
a04efe6afb63d54e12ff8f329cbaf458a2e31b26 changed the logic to use
SIGTRAP to make it possible to skip past fatal log messages in the
debugger if they weren’t relevant to the problem being debugged.

Signed-off-by: Philip Withnall <withnall@endlessm.com>
https://gitlab.gnome.org/GNOME/glib/issues/1448
glib/gbacktrace.h
glib/gmessages.c