From 45fa2529db961adff41c52c3a560808cb135beb2 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Tue, 15 Mar 2016 11:08:52 +0000 Subject: [PATCH] Document possible unreliability of '$_ret' MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit gdb/doc/ChangeLog: 2016-03-15 Pedro Alves Andreas Arnez Marcin Kościelnicki * gdb.texinfo (Tracepoint Actions): Document possible unreliability of '$_ret'. --- gdb/doc/ChangeLog | 7 +++++++ gdb/doc/gdb.texinfo | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 3d49085..0606d9d 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,10 @@ +2016-03-15 Pedro Alves + Andreas Arnez + Marcin Kościelnicki + + * gdb.texinfo (Tracepoint Actions): Document possible + unreliability of '$_ret'. + 2016-03-11 Andrew Burgess * gdb.texinfo (Symbols): Document new 'maint info line-table' diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index bf7df35..5f88335 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -12878,6 +12878,13 @@ 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 +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. +When this happens, backtracing will stop because the return address is +found unavailable (unless another collect rule happened to match it). + @item $_probe_argc Collects the number of arguments from the static probe at which the tracepoint is located. -- 2.7.4