btrace: work around _dl_runtime_resolve returning to resolved function
authorMarkus Metzger <markus.t.metzger@intel.com>
Fri, 23 Jan 2015 12:32:12 +0000 (13:32 +0100)
committerMarkus Metzger <markus.t.metzger@intel.com>
Tue, 3 Mar 2015 08:52:27 +0000 (09:52 +0100)
commit986b66010c684a871f5606cb4f074d4e3d829e2f
treea8d588c765083f9b5eac9d10809b871171a0216d
parentce0dfbeaadee82ffae390e4515433d3b6b1e0084
btrace: work around _dl_runtime_resolve returning to resolved function

On some systems, _dl_runtime_resolve returns to the resolved function
instead of jumping to it.  Since btrace will not find the function in
the current stack back trace, it will start a new back trace on the
same level.  It will look the same to the user via the backtrace
command but the frames will have different id's which confuses stepping.

This fixes a test fail with 32-bit inferior reported by Jan Kratochvil.

gdb/
* btrace.c (ftrace_update_function): Treat return as tailcall for
"_dl_runtime_resolve".
gdb/ChangeLog
gdb/btrace.c