3
info signals/handle - List all available signals
7
handle <signal> <keywords>
8
signal is #(number), name, #-#(range), all (all signals)
10
stop/nostop - Stop program when signal happens
11
print/noprint - Print message when signal happens
12
pass/nopass - Pass the signal to the debugging application or not
13
ignore/noignore - ignore is equivalent of nopass
15
- When a signal stops your program, the signal is not visible to the
16
program until you continue.
17
- After GDB reports a signal, you can use the handle command with pass or
18
nopass to control whether your program sees that signal when you continue.
21
Resume execution where your program stopped, but immediately give it the
24
If program stopped due to a signal and would ordinary see the signal when
25
resumed with the continue command; `signal 0' causes it to resume without
30
- Normaly, it could be achieved by sending SIGINT to gdb (or just presing
31
Ctrl+C). 'nopass' should be set for SIGINT (default behavior).
32
+ It is aslo possible to send SIGINT directly to app/thread pid.
33
+ The SIGINT should not be blocked in the thread of interest
35
- Unfortunatelly, seems for multithreaded applications it would not prevent
36
other threads from getting signal (at least in attach to process case).
37
+ Therefore, the best is to ignore SIGINT (set a dummy signal handler,
38
not block) in all application threads during debug. The SIGTERM could