From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2 4/5] gdb: add program_space parameter to clear_solib
Date: Fri, 9 Feb 2024 11:07:26 -0500 [thread overview]
Message-ID: <e5771ca2-7390-447e-bc7d-d707d21a2cf9@simark.ca> (raw)
In-Reply-To: <87bk8p7ker.fsf@redhat.com>
On 2024-02-09 09:59, Andrew Burgess wrote:
> Thanks for adding this last part. This was what worried me about the
> idea of a pspace -> solib_ops link, multiple gdbarch within a single
> program_space.
>
> So I'm convinced that this is the right way to go.
Cool, thanks.
Just to be clear, we can have multiple gdbarches within a pspace today
(e.g. the now-removed SPU port), we just can't have them specify
different solib_ops. Just moving to have a single pspace -> solib_ops
link wouldn't be a regression, it would just make what we have now more
explicit.
Simon
next prev parent reply other threads:[~2024-02-09 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 16:53 [PATCH v2 0/5] Random cleanup patches Simon Marchi
2024-02-07 16:53 ` [PATCH v2 1/5] gdb: add program_space parameter to mark_breakpoints_out Simon Marchi
2024-02-07 16:53 ` [PATCH v2 2/5] gdb: add inferior parameter to breakpoint_init_inferior Simon Marchi
2024-02-07 16:53 ` [PATCH v2 3/5] gdb: add program_space parameter to disable_breakpoints_in_shlibs Simon Marchi
2024-02-07 16:53 ` [PATCH v2 4/5] gdb: add program_space parameter to clear_solib Simon Marchi
2024-02-08 14:29 ` Andrew Burgess
2024-02-08 16:21 ` Simon Marchi
2024-02-09 14:59 ` Andrew Burgess
2024-02-09 16:07 ` Simon Marchi [this message]
2024-02-07 16:53 ` [PATCH v2 5/5] gdb: remove unnecessary nullptr check in remove_user_added_objfile Simon Marchi
2024-02-08 14:39 ` [PATCH v2 0/5] Random cleanup patches Andrew Burgess
2024-02-09 16:07 ` 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=e5771ca2-7390-447e-bc7d-d707d21a2cf9@simark.ca \
--to=simark@simark.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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).