diff options
| author | qiyao <qiyao> | 2011-09-07 13:36:46 +0000 |
|---|---|---|
| committer | qiyao <qiyao> | 2011-09-07 13:36:46 +0000 |
| commit | 8ac81feb44e603695f2c04f243453b159382dcf4 (patch) | |
| tree | 18ec6c537083915ed309acb0b6c0081eadf84186 /gdb/gdbthread.h | |
| parent | 44a017f92479a01b43ed9012b36ffbbf72b242b3 (diff) | |
| download | gdb-8ac81feb44e603695f2c04f243453b159382dcf4.tar.gz | |
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 0b19a8dc3c5..6baeb92c3e3 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 |