[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

["simark at simark dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=27710

--- Comment #15 from Simon Marchi <simark at simark dot ca> ---
(In reply to Tom de Vries from comment #14)
> I just stumbled upon remote_unpush_target, and it seems one remote_target
> can be associated with multiple inferiors.  So at this point I'm not sure
> how one would select the "right" inferior.

Indeed, one remote target can handle multiple inferiors (if using
extended-remote).
The right inferior in this case would be any inferior of that target.  Making
any inferior of this remote target the current inferior implicitly makes this
remote target the current one, such that target_is_non_stop_p will hit that
remote target.  If the current inferior is one that does not belong to that
remote target, then target_is_non_stop_p is really asking whether some other
unrelated target is non-stop.

So adding a call to switch_to_target_no_thread should make it work (it just
makes an arbitrary inferior of the target the current one).

Another option, instead of switching the current inferior, would be to make
target_is_non_stop accept a target:

  gdb_assert (target_is_non_stop_p (notif_state->remote));

And pass down the target to everything below.  It would be a bit more work, and
we would have to make sure everything called by target_is_non_stop_p doesn't
use the global context.

This looks like a problem that happens quite rarely though, it would be nice to
have a way to reproduce it all the time, by adding some delay somewhere or
otherwise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.