Steffen Daode Nurpmeso <sdao...@googlemail.com> added the comment:
> On my Linux box, Python 3.3 says that signal.NSIG is equal to 65
> which looks correct.
On FreeBSD NSIG only counts "old" signals (32, one 32 bit mask),
SIGRTMIN is 65 and SIGRTMAX is 126.
Our internal old signal.h states
* If we do have realtime signals, #rtmin is 35 (i.e.,
* #nsig, FreeBSD+) or something like 38 or even 40 (Linux),
* and #rtmax is most likely 64 (Linux) or 128 (FreeBSD+).
so that this seems to be somewhat constant in time.
(#rtmin: we take some of those RT sigs for internal purposes if
possible. This was maybe a bad and expensive design decision.)
> Why do you care about the default action?
* \brief Hooking program crashes (\psa crash.h crash.h\epsa).
* \note
* Installed hooks (normally) execute from within an internal
* signal handler!
So many syscalls for things which don't matter almost ever.
And that may even cost context-switches sometimes.
> I don't understand: I don't use RTMAX in my patch.
+ for (signum = 1; signum < NSIG; signum++) {
This will not catch the extended signal range on FreeBSD.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12060>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
