FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[gdb,testsuite,doc,NEWS] Fix "the the".

Browse source 
Replace "the the" by "the".

gdb/ChangeLog:

2020-03-06  Tom de Vries  <tdevries@suse.de>

	* NEWS: Fix "the the".
	* ctfread.c: Same.

gdb/doc/ChangeLog:

2020-03-06  Tom de Vries  <tdevries@suse.de>

	* gdb.texinfo: Fix "the the".

gdb/testsuite/ChangeLog:

2020-03-06  Tom de Vries  <tdevries@suse.de>

	* README: Fix "the the".
	* gdb.base/dprintf.exp: Same.
This commit is contained in:
Tom de Vries 2020-03-06 15:22:23 +01:00
parent fd760e798e
commit 09f2921cc9
8 changed files with 23 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

5
gdb/ChangeLog
View file

@ -1,3 +1,8 @@
2020-03-06 Tom de Vries <tdevries@suse.de>
* NEWS: Fix "the the".
* ctfread.c: Same.
2020-03-06 Tom de Vries <tdevries@suse.de>
* psymtab.c (psymtab_to_symtab): Don't print "done.".

6
gdb/NEWS
View file

@ -2419,7 +2419,7 @@ show code-cache
* Newly installed $prefix/bin/gcore acts as a shell interface for the
GDB command gcore.
* GDB now implements the the C++ 'typeid' operator.
* GDB now implements the C++ 'typeid' operator.
* The new convenience variable $_exception holds the exception being
thrown or caught at an exception-related catchpoint.
@ -5203,7 +5203,7 @@ The new infrastructure making possible the implementation of key new
features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
i386 application).
GDB 6.3 will be the last release to include the the registers[]
GDB 6.3 will be the last release to include the registers[]
compatibility module that allowed out-of-date configurations to
continue to work. This change directly impacts the following
configurations:
@ -6634,7 +6634,7 @@ Remote targets now use a data cache to speed up communication with the
remote side. The data cache could lead to incorrect results because
it doesn't know about volatile variables, thus making it impossible to
debug targets which use memory mapped I/O devices. `set remotecache
off' turns the the data cache off.
off' turns the data cache off.
* Remote targets may have threads

2
gdb/ctfread.c
View file

@ -45,7 +45,7 @@
The file header stores a magic number and version information, encoding
flags, and the byte offset of each of the sections relative to the end of the
header itself. If the CTF data has been uniquified against another set of
CTF data, a reference to that data also appears in the the header. This
CTF data, a reference to that data also appears in the header. This
reference is the name of the label corresponding to the types uniquified
against.

4
gdb/doc/ChangeLog
View file

@ -1,3 +1,7 @@
2020-03-06 Tom de Vries <tdevries@suse.de>
* gdb.texinfo: Fix "the the".
2020-03-04 Tom de Vries <tdevries@suse.de>
* gdb.texinfo: Remove trailing "done." in "Reading symbols from" lines.

6
gdb/doc/gdb.texinfo
View file

@ -20568,7 +20568,7 @@ when any of shared library events happen. The best way to do this is
to use @code{catch load} and @code{catch unload} (@pxref{Set
Catchpoints}).
@value{GDBN} also supports the the @code{set stop-on-solib-events}
@value{GDBN} also supports the @code{set stop-on-solib-events}
command for this. This command exists for historical reasons. It is
less useful than setting a catchpoint, because it does not allow for
conditions or commands as a catchpoint does.
@ -28980,7 +28980,7 @@ recommended that front ends request a specific version of MI when launching
@value{GDBN} (e.g. @code{--interpreter=mi2}) to make sure they get an
interpreter with the MI version they expect.
The following table gives a summary of the the released versions of the MI
The following table gives a summary of the released versions of the MI
interface: the version number, the version of GDB in which it first appeared
and the breaking changes compared to the previous version.
@ -29158,7 +29158,7 @@ The following is the list of possible async records:
@item *running,thread-id="@var{thread}"
The target is now running. The @var{thread} field can be the global
thread ID of the the thread that is now running, and it can be
thread ID of the thread that is now running, and it can be
@samp{all} if all threads are running. The frontend should assume
that no interaction with a running thread is possible after this
notification is produced. The frontend should not assume that this

5
gdb/testsuite/ChangeLog
View file

@ -1,3 +1,8 @@
2020-03-06 Tom de Vries <tdevries@suse.de>
* README: Fix "the the".
* gdb.base/dprintf.exp: Same.
2020-03-05 Tom de Vries <tdevries@suse.de>
* gdb.base/maint.exp: Update "main print statistics" expected output.

2
gdb/testsuite/README
View file

@ -197,7 +197,7 @@ a .gdbinit. For example:
GDB_PARALLEL
To use parallel testing mode without using the the Makefile, set
To use parallel testing mode without using the Makefile, set
GDB_PARALLEL on the runtest command line to "yes". Before starting
the tests, you must ensure that the directories cache, outputs, and
temp in the test suite build directory are either empty or have been

2
gdb/testsuite/gdb.base/dprintf.exp
View file

@ -160,7 +160,7 @@ proc test_agent {} {
return
}
# Even if the the target reports that it does support target side
# Even if the target reports that it does support target side
# commands, we can only tell that it supports them in combination
# with a particular breakpoint type (Z0, Z1, etc.) when we try to
# insert the breakpoint. When "set breakpoint always-inserted is