From: Pedro Alves Date: Tue, 15 Mar 2016 11:29:03 +0000 (+0000) Subject: Fix typo in previous gdb/doc/ commit X-Git-Tag: binutils-2_27~1077 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2a60e18f8fe3bf9512671e02b39acacb484bb8c6;p=external%2Fbinutils.git Fix typo in previous gdb/doc/ commit Should be s/reliability/reliably/. gdb/doc/ChangeLog: 2016-03-15 Pedro Alves * gdb.texinfo (Tracepoint Actions): Fix typo. --- diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 0606d9d..a48d1c4 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,4 +1,8 @@ 2016-03-15 Pedro Alves + + * gdb.texinfo (Tracepoint Actions): Fix typo. + +2016-03-15 Pedro Alves Andreas Arnez Marcin Kościelnicki diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 5f88335..71657b0 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -12878,7 +12878,7 @@ Collect all local variables. Collect the return address. This is helpful if you want to see more 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 collected instead. On some architectures the reliability is higher for tracepoints at function entry, while on others it's the opposite.