From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>,
Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix auxv cache clearing from new_objfile observer
Date: Mon, 6 Nov 2023 09:21:46 +0100 [thread overview]
Message-ID: <e26109e8-520a-4de8-a70d-1106164a5639@suse.de> (raw)
In-Reply-To: <2fefd58b-99bf-47de-9361-09f66165dab5@simark.ca>
On 10/3/23 19:50, Simon Marchi via Gdb-patches wrote:
>> A better solution might be to have the address spaces be reference
>> counted, then we could remove the gdbarch_has_shared_address_space
>> call completely, and just rely on the reference count to auto-delete
>> the address space when appropriate.
> I advocate for the shared_ptr / refcount solution. ~program_space is
> really not a good place to do target calls, as you noted.
I've implemented a refcount approach here (
https://sourceware.org/pipermail/gdb-patches/2023-November/203764.html ).
Thanks,
- Tom
next prev parent reply other threads:[~2023-11-06 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:20 Andrew Burgess
2023-10-03 17:50 ` Simon Marchi
2023-10-05 17:20 ` Simon Marchi
2023-11-06 8:21 ` Tom de Vries [this message]
2023-10-06 16:43 ` Andrew Burgess
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=e26109e8-520a-4de8-a70d-1106164a5639@suse.de \
--to=tdevries@suse.de \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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).