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: Wed, 14 Apr 2021 12:58:04 +0000 [thread overview]
Message-ID: <bug-27710-4717-X6nud19eLo@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 #10 from Simon Marchi <simark at simark dot ca> ---
(In reply to Tom de Vries from comment #5)
> We have:
> ...
> bool
> target_can_async_p ()
> {
> return current_inferior ()->top_target ()->can_async_p ();
> }
> ...
>
> AFAIU, current_inferior ()->top_target () translates to:
> ...
> (gdb) p
> current_inferior_.m_obj.m_target_stack.m_stack[current_inferior_.m_obj.
> m_target_stack.m_top]
> $16 = (target_ops *) 0x16c6cd0 <exec_ops>
> ...
>
> Exec_ops has type exec_target, which subclasses target_ops without
> implementing a can_async_p override, so we have the default:
> ...
> virtual bool can_async_p ()
> TARGET_DEFAULT_RETURN (false);
> ...
Since the test is related to multi-inferior, my first question would be, is the
current inferior the right one (one that belongs to the remote target receiving
the notification)?
We have the remote target in notif_state->remote_target, so maybe we need to
switch to it before calling target_is_non_stop_p. From a quick look, it
doesn't seem like remote_notif_process cares about the current inferior though.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-14 12: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 [this message]
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
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-X6nud19eLo@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: link
Be 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).