Open
Bug 794074
Opened 12 years ago
Updated 2 years ago
libevent does not support the realtime signals (i.e., signal numbers >= NSIG)
Categories
(Core :: XPCOM, defect)
Tracking
()
NEW
People
(Reporter: justin.lebar+bug, Unassigned)
References
Details
See bug 788021 comment 48. I tried to use Chromium's MessagePump::CatchSignal to catch SIGRTMIN and SIGRTMIN + 1, but it segfaults (and should assert, but the assertions seem to be disabled even in debug builds) because SIGRTMIN >= NSIG. It's not clear to me how to fix this in libevent, because the kernel docs say SIGRT{MIN,MAX} should not be treated as compile-time constants, and the number of signals is used as a compile-time constant in a variety of places in libevent.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•