From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 507C3384A033; Mon, 2 Nov 2020 10:42:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 507C3384A033 From: "nilsgladitz at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/26828] New: SIGSEGV in follow_die_offset dwarf2/read.c:22950 Date: Mon, 02 Nov 2020 10:42:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nilsgladitz at gmail dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 10:42:52 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26828 Bug ID: 26828 Summary: SIGSEGV in follow_die_offset dwarf2/read.c:22950 Product: gdb Version: 10.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: nilsgladitz at gmail dot com Target Milestone: --- I am running GDB 10.1 on x86_64 GNU/Linux targeting ARM. While debugging a core file with "-i=3Dmi" and repeatedly running e.g. "-stack-list-variables --thread 1 --frame 0 --simple-values" results in a segmentation fault. The first call returns "frame" and "variables" information. The second call returns just the "variables". The third call segfaults in "follow_die_offset" (dwarf2/read.c:22950). The segfaulting line reads: target_cu->ancestor =3D cu; target_cu is apparently 0. I can reproduce the issue with current master (e1f57067b162cba9f39e087726c7a2f2cfaae96f) too. With GDB 9.1 the third (and subsequent) calls don't seem to segfault. --=20 You are receiving this mail because: You are on the CC list for the bug.=