public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27710] remote-notif.c:113: internal-error: void remote_async_get_pending_events_handler(gdb_client_data): Assertion `target_is_non_stop_p ()' failed Date: Thu, 15 Apr 2021 17:58:05 +0000 [thread overview] Message-ID: <bug-27710-4717-H7ItJMdD7k@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27710-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27710 --- Comment #19 from Simon Marchi <simark at simark dot ca> --- I don't really understand this supposed separation of concerns between remote.c and remote-notif.c. They both know about each other: remote_target (well, remote_state) uses remote_notif_state, and remote_notif_state (and notif_client) only works with remote_target as its user. Anyway. To avoid all this churn, I'd be fine with a new util function "remote_target_is_non_stop", implemented in remote.c, like: bool remote_target_is_non_stop_p (remote_target *t) { scoped_restore_current_thread restore_thread; switch_to_target_no_thread (t); return target_is_non_stop_p (); } You could then use gdb_assert (remote_target_is_non_stop_p (remote_target)) in remote-notif.c. If / when target_is_non_stop_p becomes a method on target_ops and hopefully independent from the current context, it could be simplified to: bool remote_target_is_non_stop_p (remote_target *t) { return t->is_non_stop_p (); } -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-15 17:58 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-08 13:39 [Bug gdb/27710] New: " vries at gcc dot gnu.org 2021-04-08 13:41 ` [Bug gdb/27710] " vries at gcc dot gnu.org 2021-04-08 13:44 ` vries at gcc dot gnu.org 2021-04-08 14:02 ` simark at simark dot ca 2021-04-14 8:29 ` vries at gcc dot gnu.org 2021-04-14 8:57 ` vries at gcc dot gnu.org 2021-04-14 9:59 ` vries at gcc dot gnu.org 2021-04-14 10:12 ` vries at gcc dot gnu.org 2021-04-14 12:51 ` simark at simark dot ca 2021-04-14 12:56 ` vries at gcc dot gnu.org 2021-04-14 12:58 ` simark at simark dot ca 2021-04-14 13:13 ` simark at simark dot ca 2021-04-14 15:06 ` vries at gcc dot gnu.org 2021-04-14 15:09 ` vries at gcc dot gnu.org 2021-04-14 15:34 ` vries at gcc dot gnu.org 2021-04-14 17:03 ` simark at simark dot ca 2021-04-14 17:19 ` cbiesinger at google dot com 2021-04-14 17:20 ` simark at simark dot ca 2021-04-15 7:34 ` vries at gcc dot gnu.org 2021-04-15 17:58 ` simark at simark dot ca [this message] 2021-04-16 8:03 ` [Bug remote/27710] " vries at gcc dot gnu.org 2021-04-22 8:53 ` vries at gcc dot gnu.org 2021-04-22 15:01 ` cvs-commit at gcc dot gnu.org 2021-04-22 15:01 ` vries at gcc dot gnu.org
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-27710-4717-H7ItJMdD7k@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).