https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117320
--- Comment #3 from Paul Eggert <eggert at cs dot ucla.edu> ---
(In reply to Andrew Pinski from comment #1)
> Does it happen in a full linked binary or just in the object file?
The bug occurs in both, though of course I see different values for the
backtrace_function address in the full linked binary:
$ nm temacs | grep backtrace_function
0000000000293cd0 T backtrace_function
000000000006ee78 t backtrace_function.cold
000000000006ed5c t backtrace_function.part.0
$ gdb -ex 'print backtrace_next' -ex 'print backtrace_function' temacs
...
$1 = {union specbinding *(union specbinding *)} 0x293d70 <backtrace_next>
$2 = {Lisp_Object (union specbinding *)} 0x6ed5c <backtrace_function>
> this looks to be a gdb issue with respect to an relocated object file and not
> a debugging information produced by GCC.
Thanks, I have filed a GDB bug report
<https://sourceware.org/bugzilla/show_bug.cgi?id=32313>.
