public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28275] commit_resumed_state assertion failure when killing running inferior and running again Date: Thu, 26 Aug 2021 19:39:42 +0000 [thread overview] Message-ID: <bug-28275-4717-e8BUHo1U1q@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28275-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28275 Andrew Burgess <andrew.burgess at embecosm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.burgess at embecosm dot com --- Comment #1 from Andrew Burgess <andrew.burgess at embecosm dot com> --- Created attachment 13630 --> https://sourceware.org/bugzilla/attachment.cgi?id=13630&action=edit Patch to add a related issue into the testsuite. I ran into the same assertion while debugging some other issue. My steps to reproduce are slightly different, but I thought I'd add the details here as it feels like these two cases must be related: $ /tmp/gdb/testsuite/outputs/gdb.threads/detach-step-over/detach-step-over $ gdb (gdb) attach 608289 Attaching to program: /tmp/gdb/testsuite/outputs/gdb.threads/detach-step-over/detach-step-over, process 608289 ... snip ... [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f84068f4215 in nanosleep () from /lib64/libc.so.6 (gdb) break detach-step-over.c:54 if 0 Breakpoint 1 at 0x40119c: file /tmp/gdb/testsuite/../../../src/gdb/testsuite/gdb.threads/detach-step-over.c, line 54. (gdb) continue & Continuing. (gdb) q A debugging session is active. Inferior 1 [process 608289] will be detached. Quit anyway? (y or n) y ../../src/gdb/target.c:3778: internal-error: void target_stop(ptid_t): Assertion `!proc_target->commit_resumed_state' failed. The patch I've attached modifies gdb.threads/detach-step-over.exp to show this bug, this patch isn't ready to upstream in its current state. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-08-26 19:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-26 14:35 [Bug gdb/28275] New: " simark at simark dot ca 2021-08-26 19:39 ` andrew.burgess at embecosm dot com [this message] 2021-10-29 9:22 ` [Bug gdb/28275] " nyanpasu64 at tuta dot io 2021-10-29 12:54 ` simark at simark dot ca 2022-11-14 15:02 ` vries at gcc dot gnu.org 2022-11-14 15:29 ` simark at simark dot ca 2022-11-14 16:32 ` vries at gcc dot gnu.org 2022-11-15 7:34 ` vries at gcc dot gnu.org 2022-11-15 11:20 ` vries at gcc dot gnu.org 2022-11-15 12:55 ` vries at gcc dot gnu.org 2022-11-16 15:36 ` aburgess at redhat dot com 2022-11-22 15:29 ` brobecker at gnat dot com 2022-11-28 13:03 ` cvs-commit at gcc dot gnu.org 2022-11-28 14:13 ` cvs-commit at gcc dot gnu.org 2022-11-28 14:14 ` simark at simark dot ca 2022-12-01 15:07 ` cvs-commit at gcc dot gnu.org 2022-12-01 15:07 ` cvs-commit at gcc dot gnu.org 2023-01-04 9:15 ` vries at gcc dot gnu.org 2023-01-04 9:57 ` brobecker at gnat 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-28275-4717-e8BUHo1U1q@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).