From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F0AED3858282; Mon, 20 Nov 2023 09:54:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F0AED3858282 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1700474080; bh=F200OYaSsgdyxy7VuejYa9x9dqNpb4191Af5v6FFgIE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ny26LuNj2TuWXAK8iujU1I8wtR/ogSvhI8GehTN3vgy6ggiRxZ0GNzmF+X/6WaPqx XrAQ8syFPrHWEjZnEeNXXr3FRJ0j+/hf8rkHVyCAYaPcb6I0V72DK/VsUzWImjKtXs QBy+kfTRcTYdQgxV4CmE7TGwM2CA6UzPvkPKXNZY= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/29178] GDB wont print frame when reverse stepping out of recursive function Date: Mon, 20 Nov 2023 09:54:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29178 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Bruno Larsen : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dbf2813aff8f2= 988ad3d53e819a0415abf295c91f commit bf2813aff8f2988ad3d53e819a0415abf295c91f Author: Guinevere Larsen 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=3D29178 Approved-By: Tom Tromey --=20 You are receiving this mail because: You are on the CC list for the bug.=