[Bug backtrace/30929] New: 'frame function' fails when call is the last instruction

["amonakov at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30929

            Bug ID: 30929
           Summary: 'frame function' fails when call is the last
                    instruction
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: amonakov at gmail dot com
  Target Milestone: ---

int main()
{
        __builtin_abort();
}

gcc -g test.c

gdb ./a.out

(gdb) start
Temporary breakpoint 1 at 0x40113a: file t.c, line 3.

Temporary breakpoint 1, main () at t.c:3
3               __builtin_abort();
(gdb) f f main
#0  main () at t.c:3
3               __builtin_abort();
(gdb) c
Continuing.

Program received signal SIGABRT, Aborted.
0x00007ffff7e4d47c in __pthread_kill_implementation () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff7e4d47c in __pthread_kill_implementation () from
/lib64/libc.so.6
#1  0x00007ffff7dfae16 in raise () from /lib64/libc.so.6
#2  0x00007ffff7de389c in abort () from /lib64/libc.so.6
#3  0x000000000040113f in main () at t.c:3
(gdb) f f main
No frame for function "main".


Compiling to an intermediate assembly file and adding a nop after 'call abort'
is sufficient to make it work. Apparently 'frame function' doesn't work in the
corner case when return address is exactly past the end of a function (the last
instruction was a call).

In practice this breaks the following snippet:

catch signal SIGABRT
commands
f f __assert_fail
up
end

which is supposed to automatically select the frame of the failing assert.

-- 
You are receiving this mail because:
You are on the CC list for the bug.