espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-25 21:41:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix typo in previous gdb/doc/ commit

Browse Source 
Should be s/reliability/reliably/.

gdb/doc/ChangeLog:
2016-03-15  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Tracepoint Actions): Fix typo.
This commit is contained in:
Pedro Alves
2016-03-15 11:29:03 +00:00
parent 45fa2529db
commit 2a60e18f8f
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2016-03-15 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Tracepoint Actions): Fix typo.
2016-03-15 Pedro Alves <palves@redhat.com> 2016-03-15 Pedro Alves <palves@redhat.com>
Andreas Arnez <arnez@linux.vnet.ibm.com> Andreas Arnez <arnez@linux.vnet.ibm.com>
Marcin Kościelnicki <koriakin@0x04.net> Marcin Kościelnicki <koriakin@0x04.net>

2
gdb/doc/gdb.texinfo
View File

@ -12878,7 +12878,7 @@ Collect all local variables.
Collect the return address. This is helpful if you want to see more Collect the return address. This is helpful if you want to see more
of a backtrace. of a backtrace.
@emph{Note:} The return address location can not always be reliability @emph{Note:} The return address location can not always be reliably
determined up front, and the wrong address / registers may end up determined up front, and the wrong address / registers may end up
collected instead. On some architectures the reliability is higher collected instead. On some architectures the reliability is higher
for tracepoints at function entry, while on others it's the opposite. for tracepoints at function entry, while on others it's the opposite.