JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

New entry (Programming Questions): 'Why doesn't gdb handle signals?'

Browse Source
This commit is contained in:
David Starks-Browning 2000-07-25 21:35:08 +00:00
parent 53d1fe2a5c
commit 738c2431e5
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
winsup/doc/how.texinfo
View File

@ -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