From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 41900385840F; Thu, 23 Feb 2023 23:12:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 41900385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677193921; bh=CUMADG0or5S4Lpl1IKrvsMqbYOmck7rrYbMwqk1wkwo=; h=From:To:Subject:Date:From; b=hJOJvns/zMYFvgEUPBPw/acADBaujM49C2a8WxS+JdmO8Jnct6sP2G86R5cc2EP65 vGAae3ZykUs6SjyvV9WeEJKWrhh2FhQer5k6mbh2tCjIYPOU0uGPKcNfpwqICeuOhV c1ZTrxE8+CRMkvj4fm6dmjKjsUumvBNdeUmTF0Tw= From: "saemy at optumsoft dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30160] New: Assertion failure in dummy_frame_pop(frame_id, thread_info*) Date: Thu, 23 Feb 2023 23:12:00 +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: 11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: saemy at optumsoft 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30160 Bug ID: 30160 Summary: Assertion failure in dummy_frame_pop(frame_id, thread_info*) Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: saemy at optumsoft dot com Target Milestone: --- Consider the following setup: (a) Run some process; say with pid 1234 (b) Have the following file "my.gdbscript": """ define hook-stop call (int) printf("foo") end """ The following then produces an assertion failure on gdb 11.1 and newer (whi= le working fine on 10.2): ``` $ gdb --init-command=3Dmy.gdbscript --pid=3D1234 [...] dummy-frame.c:212: internal-error: void dummy_frame_pop(frame_id, thread_info*): Assertion `dp !=3D NULL' failed. [...] ``` In the newer versions there seem to be two calls to `dummy_frame_pop()` for= the same frame_id when there is only one such call in the older versions. I have added two backtraces to this bug; (1) bt-both.txt contains the backtrace of the call that is there both in 10= .2 and 11.1 (2) bt-new.txt contains the backtrace of the additional call that is only around in 11.1 and newer. Thank you for your help. --=20 You are receiving this mail because: You are on the CC list for the bug.=