public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/28077] -exec-interrupt in non-stop mode causes internal-error / assertion in target_stop Date: Sun, 11 Jul 2021 19:42:32 +0000 [thread overview] Message-ID: <bug-28077-4717-3yReJuAikq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28077-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28077 --- Comment #1 from Jonah Graham <jonah at kichwacoders dot com> --- The commit that caused the regression is 1192f124a308601f5fef7a35715ccd6f904e7b17 Note that "interrupt" or "-exec-interrupt" without the --thread-group argument does not cause this to fail. Here is my oneliner to check (part of my git bisect script): (sleep .5s ; echo '-gdb-set non-stop on' ; echo '-gdb-set mi-async on' ; echo '-file-exec-and-symbols --thread-group i1 loop' ; echo '-exec-run' ; sleep .5s ; echo '-exec-interrupt --thread-group i1') | gdb/gdb --interpreter=mi2 The above asserts, but the below doesn't (without the --thread-group): (sleep .5s ; echo '-gdb-set non-stop on' ; echo '-gdb-set mi-async on' ; echo '-file-exec-and-symbols --thread-group i1 loop' ; echo '-exec-run' ; sleep .5s ; echo '-exec-interrupt') | gdb/gdb --interpreter=mi2 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-11 19:42 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-11 19:05 [Bug mi/28077] New: " jonah at kichwacoders dot com 2021-07-11 19:42 ` jonah at kichwacoders dot com [this message] 2021-07-12 0:22 ` [Bug mi/28077] " simark at simark dot ca 2021-07-12 0:39 ` simark at simark dot ca 2021-07-12 1:04 ` jonah at kichwacoders dot com 2021-07-12 2:10 ` jonah at kichwacoders dot com 2021-07-12 2:17 ` simark at simark dot ca 2021-07-12 2:17 ` simark at simark dot ca 2021-07-12 2:17 ` simark at simark dot ca 2021-07-12 2:17 ` simark at simark dot ca 2021-07-13 13:26 ` cvs-commit at gcc dot gnu.org 2021-07-13 13:27 ` cvs-commit at gcc dot gnu.org 2021-07-13 13:37 ` simark at simark dot ca
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-28077-4717-3yReJuAikq@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).