diff options
| author | Yao Qi <yao@codesourcery.com> | 2011-09-07 13:36:47 +0000 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2011-09-07 13:36:47 +0000 |
| commit | 6aa27652a77b5dba33707448c56ec538249a0f6e (patch) | |
| tree | 869f13a1f7ae7890e99e0dad5d3e6f7708abf7b2 /gdb/gdbthread.h | |
| parent | 00db5b9440bd7b0fc8581e28efe8601891d1f29c (diff) | |
| download | gdb-6aa27652a77b5dba33707448c56ec538249a0f6e.zip gdb-6aa27652a77b5dba33707448c56ec538249a0f6e.tar.gz gdb-6aa27652a77b5dba33707448c56ec538249a0f6e.tar.bz2 | |
gdb/
* gdbthread.h (struct thread_info): Comment on field
`step_after_step_resume_breakpoint'.
Diffstat (limited to 'gdb/gdbthread.h')
| -rw-r--r-- | gdb/gdbthread.h | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h index 0b19a8d..6baeb92 100644 --- a/gdb/gdbthread.h +++ b/gdb/gdbthread.h @@ -176,7 +176,14 @@ struct thread_info int stepping_over_breakpoint; /* Set to TRUE if we should finish single-stepping over a breakpoint - after hitting the current step-resume breakpoint. */ + after hitting the current step-resume breakpoint. The context here + is that GDB is to do `next' or `step' while signal arrives. + When stepping over a breakpoint and signal arrives, GDB will attempt + to skip signal handler, so it inserts a step_resume_breakpoint at the + signal return address, and resume inferior. + step_after_step_resume_breakpoint is set to TRUE at this moment in + order to keep GDB in mind that there is still a breakpoint to step over + when GDB gets back SIGTRAP from step_resume_breakpoint. */ int step_after_step_resume_breakpoint; /* This is set TRUE when a catchpoint of a shared library event |