From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Lancelot SIX <lsix@lancelotsix.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/6] Rewrite registry.h
Date: Wed, 08 Jun 2022 12:51:44 -0600 [thread overview]
Message-ID: <87v8tb0z0f.fsf@tromey.com> (raw)
In-Reply-To: <878rq82b22.fsf@tromey.com> (Tom Tromey's message of "Tue, 07 Jun 2022 19:33:57 -0600")
Tom> This particular failure comes because the order of destruction of the
Tom> per-bfd and per-objfile objects changed. I think it's better to avoid
Tom> this problem entirely. I've got a patch to do this that I will send
Tom> soon.
Tom> After that's in, I'll rebase the registry series and test it with ASAN.
This series helped but there are still a couple of issues.
One I haven't investigated and I suspect it's pre-existing. I'll look
soon.
The other I think will benefit from:
https://sourceware.org/pipermail/gdb-patches/2022-June/189818.html
So I will at least wait for that to go in.
Tom
next prev parent reply other threads:[~2022-06-08 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 17:59 [PATCH 0/6] " Tom Tromey
2022-05-30 17:59 ` [PATCH 1/6] Change address_space to use new and delete Tom Tromey
2022-05-30 17:59 ` [PATCH 2/6] Change allocation of type-copying hash table Tom Tromey
2022-05-30 17:59 ` [PATCH 3/6] Remove some unused functions from guile code Tom Tromey
2022-05-30 17:59 ` [PATCH 4/6] Rewrite registry.h Tom Tromey
2022-06-07 10:55 ` Lancelot SIX via Gdb-patches
2022-06-08 1:33 ` Tom Tromey
2022-06-08 18:51 ` Tom Tromey [this message]
2022-05-30 17:59 ` [PATCH 5/6] Change registry to use less memory Tom Tromey
2022-05-30 17:59 ` [PATCH 6/6] Remove some unneeded checks in Guile code Tom Tromey
2022-07-28 20:13 ` [PATCH 0/6] Rewrite registry.h Tom Tromey
2022-07-29 2:33 ` Simon Marchi via Gdb-patches
2022-08-02 2:46 ` Tom Tromey
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=87v8tb0z0f.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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