[Bug gdb/16678] record problem with recursion

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

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

--- Comment #2 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=1f3e37e057e876b37db49dbd8ed5ca22c33f6772

commit 1f3e37e057e876b37db49dbd8ed5ca22c33f6772
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Wed May 25 15:02:47 2022 -0300

    gdb/reverse: Fix stepping over recursive functions

    Currently, when using GDB to do reverse debugging, if we try to use the
    command "reverse next" to skip a recursive function, instead of skipping
    all of the recursive calls and stopping in the previous line, we stop at
    the second to last recursive call, and need to manually step backwards
    until we leave the first call.  This is well documented in PR gdb/16678.

    This bug happens because when GDB notices that a reverse step has
    entered into a function, GDB will add a step_resume_breakpoint at the
    start of the function, then single step out of the prologue once that
    breakpoint is hit.  The problem was happening because GDB wouldn't give
    that step_resume_breakpoint a frame-id, so the first time the breakpoint
    was hit, the inferior would be stopped.  This is fixed by giving the
    current frame-id to the breakpoint.

    This commit also changes gdb.reverse/step-reverse.c to contain a
    recursive function and attempt to both, skip it altogether, and to skip
    the second call from inside the first call, as this setup broke a
    previous version of the patch.

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