[Bug gdb/25272] New: [RFE] On debuggee crashes/signals, go to last frame with known sources

hi-angel at yandex dot ru sourceware-bugzilla@sourceware.org
Thu Dec 12 12:58:00 GMT 2019


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

            Bug ID: 25272
           Summary: [RFE] On debuggee crashes/signals, go to last frame
                    with known sources
           Product: gdb
           Version: 8.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: hi-angel at yandex dot ru
  Target Milestone: ---

Usually, when something happens under gdb, such as segfault, assert, etc, gdb
stays at the frame where it happened, which in cases listed has no source code,
and is rarely interesting.

So a programmer has to evaluate `bt`, look what was the last frame with known
sources, and go there.

It would be more practical if gdb has an opt-out option, which would cause gdb
to automatically jump to the last frame that has sources. Preferably, with an
informational print about it (to not confuse people who're used to the older
behavior).

Bonus points: if the option could be configured to do that not only for
crashes/signals, but for breakpoints as well. I'm often working with address
sanitizer, which requires to set breakpoint to its internal functions, and then
again to switch to the last frame with known source code.

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


More information about the Gdb-prs mailing list