public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "saemy at optumsoft dot com" <sourceware-bugzilla@sourceware.org> 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 [thread overview] Message-ID: <bug-30160-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30160 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 (while working fine on 10.2): ``` $ gdb --init-command=my.gdbscript --pid=1234 [...] dummy-frame.c:212: internal-error: void dummy_frame_pop(frame_id, thread_info*): Assertion `dp != 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. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-02-23 23:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-23 23:12 saemy at optumsoft dot com [this message] 2023-02-23 23:12 ` [Bug gdb/30160] " saemy at optumsoft dot com 2023-02-23 23:13 ` saemy at optumsoft dot com 2023-02-23 23:13 ` saemy at optumsoft dot com 2023-04-11 6:36 ` saemy at optumsoft dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30160-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).