From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27769] XML reader shares a corpus object between corpora
Date: Tue, 27 Apr 2021 11:32:09 +0000 [thread overview]
Message-ID: <bug-27769-9487-eUfIwsR1VN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27769-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27769
--- Comment #2 from Giuliano Procida <gprocida+abigail at google dot com> ---
I did a little more digging and now have a short series of patches that address
the problem here as well as a follow-up issue, plus a tiny bit of DWARF reader
cleanup. The patches are together as they all relate to corpus object creation.
See https://sourceware.org/pipermail/libabigail/2021q2/003396.html.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-27 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 7:52 [Bug default/27769] New: " gprocida+abigail at google dot com
2021-04-23 15:31 ` [Bug default/27769] " gprocida+abigail at google dot com
2021-04-27 11:32 ` gprocida+abigail at google dot com [this message]
2021-08-23 8:59 ` gprocida at google dot com
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=bug-27769-9487-eUfIwsR1VN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/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).