[Bug record/29178] GDB wont print frame when reverse stepping out of recursive function

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Bruno Larsen <blarsen@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bf2813aff8f2988ad3d53e819a0415abf295c91f

commit bf2813aff8f2988ad3d53e819a0415abf295c91f
Author: Guinevere Larsen <blarsen@redhat.com>
Date:   Fri Sep 1 13:47:32 2023 +0200

    gdb/record: print frame information when exiting a recursive call

    Currently,  when GDB is reverse stepping out of a function into the same
    function due to a recursive call, it doesn't print frame information, as
    reported by PR record/29178. This happens because when the inferior
    leaves the current frame, GDB decides to refresh the step information,
    clobbering the original step_frame_id, making it impossible to figure
    out later on that the frame has been changed.

    This commit changes GDB so that, if we notice we're in this exact
    situation, we won't refresh the step information.

    Because of implementation details, this change can cause some debug
    information to be read when it normally wouldn't before, which showed up
    as a regression on gdb.dwarf2/dw2-out-of-range-end-of-seq. Since that
    isn't a problem, the test was changed to allow for the new output.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29178
    Approved-By: Tom Tromey <tom@tromey.com>

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