From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb/remote: return early from remote_check_symbols if waiting for stop reply
Date: Fri, 29 Apr 2022 11:56:53 -0400 [thread overview]
Message-ID: <71f7ff37-4395-8c2c-6eaa-a7827387da15@polymtl.ca> (raw)
In-Reply-To: <622785b8-ed10-e0d2-f24d-45990ec9ea9c@palves.net>
> remote_new_objfile has another reference to current_inferior():
>
> /* Function to be called whenever a new objfile (shlib) is detected. */
> static void
> remote_new_objfile (struct objfile *objfile)
> {
> ...
> if (current_inferior ()->in_initial_library_scan)
> return;
>
> remote->remote_check_symbols ();
> }
>
> so seems to me that it should be here that we'd loop over inferiors.
Ok, I'll make a v2 with that.
Simon
next prev parent reply other threads:[~2022-04-29 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 3:20 [PATCH 0/2] Fix regressions caused by prune_threads patch Simon Marchi
2022-04-24 3:20 ` [PATCH 1/2] gdb/infrun: make fetch_inferior_event restore thread if exited or signalled Simon Marchi
2022-04-25 17:21 ` Andrew Burgess
2022-04-26 12:43 ` Simon Marchi
2022-04-29 12:37 ` Pedro Alves
2022-04-29 13:25 ` Simon Marchi
2022-04-24 3:20 ` [PATCH 2/2] gdb/remote: return early from remote_check_symbols if waiting for stop reply Simon Marchi
2022-04-26 10:27 ` Andrew Burgess
2022-04-26 14:15 ` Simon Marchi
2022-04-27 10:11 ` Andrew Burgess
2022-04-27 14:01 ` Simon Marchi
2022-04-29 12:50 ` Pedro Alves
2022-04-29 14:53 ` Simon Marchi
2022-04-29 15:39 ` Pedro Alves
2022-04-29 15:56 ` Simon Marchi [this message]
2022-04-29 15:47 ` Pedro Alves
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=71f7ff37-4395-8c2c-6eaa-a7827387da15@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).