From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1F8D33858425; Fri, 23 Dec 2022 16:01:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F8D33858425 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1671811294; bh=FPR1rU679KI+Se+d0Fkw8O6a5TBr7mGcuz8XzywqV24=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nFlgcKWfYj/9ZarF6nzjOGWAUJkLdndYvJecp4FOAPTrrZIaX5lZI+7uyEgK7sl5A +GNOYKovpMjVyq07/OkSfnoSSPquLQOkjQwNjIXXLmbtCG1TN3yzvKuTQ6cmRBqSiN PYTahflf5H1cvEGUtlaQN28fBz+dbo2kGBFSWv/8= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug fortran/29937] Stepping Fortran(77) code always jumps back to subroutine header Date: Fri, 23 Dec 2022 16:01:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: fortran X-Bugzilla-Version: 8.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED 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: cc 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=3D29937 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- > For every `next` step in gdb, the debugger jumps to the corresponding sub= routine > header and I need to enter `next` again to go the the actual next line/st= atement. Normally this kind of thing turns out to be a problem in the debuginfo, and not in gdb. Sometimes you can see this by using "disassemble/s" on the function in question. Otherwise, where I would normally start is by examining the line table with "readelf -wL". --=20 You are receiving this mail because: You are on the CC list for the bug.=