This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients nadeem.vawda, pitrou, sdaoden, vstinner
Date 2011-05-12.12:47:42
SpamBayes Score 2.109891e-08
Marked as misclassified No
Message-id <1305204463.81.0.983075088463.issue12060@psf.upfronthosting.co.za>
In-reply-to
Content
> Yeah it will not work without atomic ops.

... Or we can maybe block the signals (all signals or just one signal?) using pthread_sigmask(SIG_BLOCK) while we access the Handlers array. But pthread_sigmask() is not available on all OSes.

On my Linux box, Python 3.3 says that signal.NSIG is equal to 65 which looks correct.

> does anyone actually know why the last time i looked after this
> (on Linux, then) realtime signals had a default action EQ SIGABRT?

The manpage says "The default action for an unhandled real-time signal is to terminate the receiving process." It is an arbitrary choice. Why do you care about the default action?

> The NSIG detection of Modules/signalmodule.c uses 64 as a fallback.
> 32 seems to be more reasonable.
> And you test against it instead of RTMAX in the patch.

I don't understand: I don't use RTMAX in my patch.
History
Date User Action Args
2011-05-12 12:47:43vstinnersetrecipients: + vstinner, pitrou, nadeem.vawda, sdaoden
2011-05-12 12:47:43vstinnersetmessageid: <1305204463.81.0.983075088463.issue12060@psf.upfronthosting.co.za>
2011-05-12 12:47:43vstinnerlinkissue12060 messages
2011-05-12 12:47:42vstinnercreate