mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-01-04 19:10:37 -08:00
Code Issues Projects Releases Wiki Activity

Warn users not to mask sigxcpu and sigxfsz.

Browse source 
Copied from Perforce
 Change: 182901
 ServerID: perforce.ravenbrook.com
This commit is contained in:
Gareth Rees 2013-07-03 11:21:14 +01:00
parent d64998d656
commit d7d8ffdacf
1 changed files with 12 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

21
mps/manual/source/topic/thread.rst
View file

@ -62,10 +62,12 @@ than this. See the documentation for the pool class.
them signals. There's a shortage of available signals that aren't
already dedicated to other purposes (for example, LinuxThreads
uses ``SIGUSR1`` and ``SIGUSR2``), so the MPS uses ``SIGXCPU`` and
``SIGXFSZ``. This means that a program that handles these signals
needs to co-operate with the MPS.
``SIGXFSZ``. This means that programs must not mask these two
signals.
The mechanism for co-operation is currently undocumented: please
If your program needs to handle these signals, then it must
co-operate with the MPS. At present, there's no documented
mechanism for co-operating: if you are in this situation, please
:ref:`contact us <contact>`.
@ -82,13 +84,14 @@ result from barrier hits.
.. warning::
The use of barriers has the consequence that a program that
handles ``SIGBUS`` (on OS X), ``SIGSEGV`` (on FreeBSD or Linux),
or first-chance exceptions (on Windows) needs to co-operate with
the MPS.
Your program must not mask ``SIGBUS`` (on OS X) or ``SIGSEGV`` (on
FreeBSD or Linux).
The mechanism for co-operation is currently undocumented: please
:ref:`contact us <contact>`.
If your program needs to handle these signals, or handle
first-chance exceptions (on Windows), then it must co-operate with
the MPS. At present, there's no documented mechanism for
co-operating: if you are in this situation, please :ref:`contact
us <contact>`.
.. index::