SIGQUIT is fine, then I can use it to break a program (C-) and get a backtrace. :)
But please catch it in Hilfe too then, so the terminal doesn't go wacky just because I wanted a backtrace.
/ Mirar
Previous text:
2003-10-02 17:43: Subject: Some tasks from the conference
I can easily add it to 7.5 CVS. Currently my code breaks on the following signals:
signal(SIGILL, print_backtrace); signal(SIGQUIT, print_backtrace); signal(SIGABRT, print_backtrace); signal(SIGFPE, print_backtrace); signal(SIGSEGV, print_backtrace); signal(SIGBUS, print_backtrace); #ifdef SIGSYS signal(SIGSYS, print_backtrace); #endif
We want to remove SIGQUIT (which I use for debugging) since it's not strictly an error. Are the other ones ok to use as is? Note that it only, as far as I know, dumps the current thread.
/ David Hedbor