From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] gdb/remote: iterate on pspace inferiors in remote_new_objfile
Date: Wed, 4 May 2022 13:04:00 +0100 [thread overview]
Message-ID: <3b089300-e2bf-ada5-f5f5-1f4a3d54c3ad@palves.net> (raw)
In-Reply-To: <20220430032115.524232-2-simon.marchi@polymtl.ca>
On 2022-04-30 04:21, Simon Marchi via Gdb-patches wrote:
> To fix this, make remote_new_objfile iterate on all inferiors bound to
> the affected program space. Remove the target_has_execution check from
> remote_check_symbols, replace it with an assert. All callers must
> ensure that the current inferior has execution before calling it.
OK.
next prev parent reply other threads:[~2022-05-04 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 3:21 [PATCH v2 0/2] Fix regressions caused by prune_threads patch Simon Marchi
2022-04-30 3:21 ` [PATCH v2 1/2] gdb/remote: iterate on pspace inferiors in remote_new_objfile Simon Marchi
2022-05-04 12:04 ` Pedro Alves [this message]
2022-05-04 12:17 ` Simon Marchi
2022-04-30 3:21 ` [PATCH v2 2/2] gdb/remote: send qSymbol to all inferiors on startup Simon Marchi
2022-05-04 12:03 ` Pedro Alves
2022-05-04 12:25 ` Simon Marchi
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=3b089300-e2bf-ada5-f5f5-1f4a3d54c3ad@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).