From 738c2431e5f83a1a7be708b083abc106369f6799 Mon Sep 17 00:00:00 2001 From: David Starks-Browning Date: Tue, 25 Jul 2000 21:35:08 +0000 Subject: [PATCH] New entry (Programming Questions): 'Why doesn't gdb handle signals?' --- winsup/doc/how.texinfo | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/winsup/doc/how.texinfo b/winsup/doc/how.texinfo index d11f8c8df..b892b8bdd 100644 --- a/winsup/doc/how.texinfo +++ b/winsup/doc/how.texinfo @@ -1251,6 +1251,14 @@ for signal/process handling-related info, to name two. The strace mechanism is well documented in the Cygwin library sources in the file winsup/include/sys/strace.h. +@subsection Why doesn't gdb handle signals? + +Unfortunately, there is only minimal signal handling support in gdb +currently. Signal handling only works with Windows-type signals. +SIGINT may work, SIGFPE may work, SIGSEGV definitely does. You cannot +'stop', 'print' or 'nopass' signals like SIGUSR1 or SIGHUP to the +process being debugged. + @subsection The linker complains that it can't find something. @strong{(Please note: This section has not yet been updated for the latest -- 2.43.5