Page MenuHomePhabricator

Switch default disposition of realtime signals

Authored by labath on Sep 11 2015, 2:05 AM.



Realtime signals generally do not represent an error condition in an application but are more
like a regular means of IPC. As such, we shouldn't interrupt an application whenever it recieves
one. If any application will use these signals, it will probably use them a lot, rendering it's
debugging tiresome if we stopped at every signal. Furthermore, these signals are likely to be used
in a low level library, and the programmer may not even be aware of their presence.

For these reasons, I am switching the default disposition of realtime signals on all supported
platforms (i.e. Linux and Freebsd) to no-stop, no-notify. Any user still wishing to receive these
signals can always change the default to suit his needs.

Diff Detail


Event Timeline

labath updated this revision to Diff 34534.Sep 11 2015, 2:05 AM
labath retitled this revision from to Switch default disposition of realtime signals.
labath updated this object.
labath added reviewers: ovyalov, emaste.
labath added a subscriber: lldb-commits.
ovyalov accepted this revision.Sep 11 2015, 10:04 AM
ovyalov edited edge metadata.


This revision is now accepted and ready to land.Sep 11 2015, 10:04 AM
sas accepted this revision.Sep 11 2015, 12:00 PM
sas added a reviewer: sas.
sas added a subscriber: sas.

Nice. I remember having similar issues with google-perftools delivering a bunch of SIGPROFs.

This revision was automatically updated to reflect the committed changes.