Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

Fix/Update misc comments

Browse Source 
While doing some investigation of mine, i noticed a few typos,
inaccuracies and missing information.

I went ahead and updated/improved those.

gdb/ChangeLog:

2020-01-14  Luis Machado  <luis.machado@linaro.org>

	* inf-ptrace.c (inf_ptrace_target::resume): Update comments.
	* infrun.c (resume_1): Likewise.
	(handle_inferior_event): Remove stale comment.
	* linux-nat.c (linux_nat_target::resume): Update comments.
	(save_stop_reason): Likewise.
	(linux_nat_filter_event): Likewise.
	* linux-nat.h (struct lwp_info) <stop_pc>, <stop_reason>: Likewise.
This commit is contained in:
Luis Machado
2019-12-06 18:12:37 -03:00
parent 7a6bf3becb
commit 7da6a5b938
5 changed files with 24 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/linux-nat.h
View File

@@ -229,7 +229,7 @@ struct lwp_info
/* When 'stopped' is set, this is where the lwp last stopped, with
decr_pc_after_break already accounted for. If the LWP is
running, and stepping, this is the address at which the lwp was
running and stepping, this is the address at which the lwp was
resumed (that is, it's the previous stop PC). If the LWP is
running and not stepping, this is 0. */
CORE_ADDR stop_pc;
@@ -238,7 +238,7 @@ struct lwp_info
int step;
/* The reason the LWP last stopped, if we need to track it
(breakpoint, watchpoint, etc.) */
(breakpoint, watchpoint, etc.). */
enum target_stop_reason stop_reason;
/* On architectures where it is possible to know the data address of