diff options
| author | David Starks-Browning <starksb@ebi.ac.uk> | 2000-07-26 01:35:08 +0400 |
|---|---|---|
| committer | David Starks-Browning <starksb@ebi.ac.uk> | 2000-07-26 01:35:08 +0400 |
| commit | 738c2431e5f83a1a7be708b083abc106369f6799 (patch) | |
| tree | f38ddbc3b6c666ec3039a83dead6059ef2883992 | |
| parent | 53d1fe2a5c02985794abc5e7d6ae37592d29eff9 (diff) | |
New entry (Programming Questions): 'Why doesn't gdb handle signals?'
| -rw-r--r-- | winsup/doc/how.texinfo | 8 |
1 files changed, 8 insertions, 0 deletions
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 <CODE>winsup/include/sys/strace.h</CODE>. +@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 |