As of Python 3.5, the signal constants are defined as an enum, enabling a nicer approach: import signal catchable_sigs = set(signal.Signals) – {signal.SIGKILL, signal.SIGSTOP} for sig in catchable_sigs: signal.signal(sig, print) # Substitute handler of choice for `print`
Signal handlers are per-process state – that is, all the threads in a process share the same set of installed signal handler functions. Signal masks are per-thread state. Signals can be blocked or unblocked on a per-thread basis. Signals can be process- or thread-directed. If a signal is process-directed, then an arbitrary thread which does … Read more
The second parameter of signal should be a pointer to a function accepting an int and returning void. What you’re passing to signal is a pointer to a member function accepting an int and returning void (its type being void (myClass::*)(int)). I can see three possibilities to overcome this issue: 1 – Your method myHandler … Read more
You can’t have data of your own passed to the signal handler as parameters. Instead you’ll have to store your parameters in global variables. (And be really, really careful if you ever need to change those data after installing the the signal handler). Response to edit 0: Historical reasons. Signals are a really old and … Read more
It’s not very pretty, but I had to do something similar in a cross-platform way, and I came up with using a separate thread. Signal based systems did not work on all platforms reliably. Use of this class could be wrapped up in a decorator, or made into a with context handler. YMMV. #!/usr/bin/env python2.7 … Read more
This was added to the documentation when Django 1.7 was released: Strictly speaking, signal handling and registration code can live anywhere you like, although it’s recommended to avoid the application’s root module and its models module to minimize side-effects of importing code. In practice, signal handlers are usually defined in a signals submodule of the … Read more
The default action for things like SIGSEGV is to terminate your process but as you’ve installed a handler for it, it’ll call your handler overriding the default behavior. But the problem is segfaulting instruction may be retried after your handler finishes and if you haven’t taken measures to fix the first seg fault, the retried … Read more
When your signal handler returns (assuming it doesn’t call exit or longjmp or something that prevents it from actually returning), the code will continue at the point the signal occurred, reexecuting the same instruction. Since at this point, the memory protection has not been changed, it will just throw the signal again, and you’ll be … Read more