public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "nyanpasu64 at tuta dot io" <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: Fri, 29 Oct 2021 09:22:31 +0000 [thread overview] Message-ID: <bug-28275-4717-IS2Q0TtuIf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28275-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28275 nyanpasu64 at tuta dot io changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nyanpasu64 at tuta dot io --- Comment #2 from nyanpasu64 at tuta dot io --- I found another procedure to reach the same crash: - Run a multithreaded GUI app (eg. gdb kwrite). - Start the application (type run). - In another terminal, call `killall kwrite` or similar. GDB will say "Thread 1 "kwrite" received signal SIGTERM, Terminated." - Type continue into gdb. gdb will say [Thread ... (LWP ...) exited], but not [Inferior 1 (process ...) exited ...], even though the PID no longer exists in /proc/NUMBER. - Type kill. When gdb asks "Kill the program being debugged? (y or n)", say y. gdb will say [Inferior 1 (process ...) killed]. - Type run. This results in the same error: target.c:2603: internal-error: ptid_t target_wait(ptid_t, target_waitstatus*, target_wait_flags): Assertion `!proc_target->commit_resumed_state' failed. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-29 9:22 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 ` [Bug gdb/28275] " andrew.burgess at embecosm dot com 2021-10-29 9:22 ` nyanpasu64 at tuta dot io [this message] 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-IS2Q0TtuIf@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).