darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2024-11-30 23:40:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

gdb/

Browse Source 
* gdbthread.h (struct thread_info): Comment on field
	`step_after_step_resume_breakpoint'.
This commit is contained in:
Yao Qi 2011-09-07 13:36:47 +00:00
parent 00db5b9440
commit 6aa27652a7
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
2011-09-07 Yao Qi <yao@codesourcery.com>
* gdbthread.h (struct thread_info): Comment on field
`step_after_step_resume_breakpoint'.
2011-09-07 Abhijit Halder <abhijit.k.halder@gmail.com>
* remote.c (remote_console_output): Reindent.

9
gdb/gdbthread.h
View File

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