OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

gdb: change "nonzero" to "true" in comments 

These int fields have been converted to bool, so their doc should say
"true" and not "nonzero".

gdb/ChangeLog:

	* breakpoint.h (bp_location) <inserted, permanent, duplicate>:
	Change "nonzero" to "true" in documentation.
This commit is contained in:
Simon Marchi 2019-09-21 19:45:12 -04:00
parent 626ca2c06f
commit 9252448ba9
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
2019-09-21 Simon Marchi <simon.marchi@polymtl.ca>
* breakpoint.h (bp_location) <inserted, permanent, duplicate>:
Change "nonzero" to "true" in documentation.
2019-09-20 Christian Biesinger <cbiesinger@google.com>
* solib-darwin.c (darwin_lookup_lib_symbol): Remove.

6
gdb/breakpoint.h
View File

@ -387,17 +387,17 @@ public:
/* Is this particular location enabled. */
bool enabled = false;
/* Nonzero if this breakpoint is now inserted. */
/* True if this breakpoint is now inserted. */
bool inserted = false;
/* Nonzero if this is a permanent breakpoint. There is a breakpoint
/* True if this is a permanent breakpoint. There is a breakpoint
instruction hard-wired into the target's code. Don't try to
write another breakpoint instruction on top of it, or restore its
value. Step over it using the architecture's
gdbarch_skip_permanent_breakpoint method. */
bool permanent = false;
/* Nonzero if this is not the first breakpoint in the list
/* True if this is not the first breakpoint in the list
for the given address. location of tracepoint can _never_
be duplicated with other locations of tracepoints and other
kinds of breakpoints, because two locations at the same