Add comments to currently_stepping and target_resume
Clarify that currently_stepping works at a higher level than target_resume. gdb/ChangeLog: 2015-08-07 Pedro Alves <palves@redhat.com> * infrun.c (currently_stepping): Extend intro comment. * target.h (target_resume): Extend intro comment.
This commit is contained in:
parent
1afd5965ed
commit
8b06156348
@ -1,3 +1,8 @@
|
||||
2015-08-07 Pedro Alves <palves@redhat.com>
|
||||
|
||||
* infrun.c (currently_stepping): Extend intro comment.
|
||||
* target.h (target_resume): Extend intro comment.
|
||||
|
||||
2015-08-07 Pedro Alves <palves@redhat.com>
|
||||
|
||||
* infrun.c (switch_back_to_stepped_thread): Use ecs->ptid instead
|
||||
|
@ -5854,7 +5854,9 @@ switch_back_to_stepped_thread (struct execution_control_state *ecs)
|
||||
return 0;
|
||||
}
|
||||
|
||||
/* Is thread TP in the middle of single-stepping? */
|
||||
/* Is thread TP in the middle of (software or hardware)
|
||||
single-stepping? (Note the result of this function must never be
|
||||
passed directly as target_resume's STEP parameter.) */
|
||||
|
||||
static int
|
||||
currently_stepping (struct thread_info *tp)
|
||||
|
@ -1292,8 +1292,8 @@ extern void target_detach (const char *, int);
|
||||
extern void target_disconnect (const char *, int);
|
||||
|
||||
/* Resume execution of the target process PTID (or a group of
|
||||
threads). STEP says whether to single-step or to run free; SIGGNAL
|
||||
is the signal to be given to the target, or GDB_SIGNAL_0 for no
|
||||
threads). STEP says whether to hardware single-step or to run free;
|
||||
SIGGNAL is the signal to be given to the target, or GDB_SIGNAL_0 for no
|
||||
signal. The caller may not pass GDB_SIGNAL_DEFAULT. A specific
|
||||
PTID means `step/resume only this process id'. A wildcard PTID
|
||||
(all threads, or all threads of process) means `step/resume
|
||||
|
Loading…
Reference in New Issue
Block a user