From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Avoid hash table corruption in gdb_bfd.c
Date: Tue, 08 Sep 2020 10:24:23 -0600 [thread overview]
Message-ID: <878sdkkzig.fsf@tromey.com> (raw)
In-Reply-To: <87mu20l01y.fsf@tromey.com> (Tom Tromey's message of "Tue, 08 Sep 2020 10:12:41 -0600")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> gdb/ChangeLog
Tom> 2020-01-14 Tom Tromey <tromey@adacore.com>
Tom> PR win32/25302:
Tom> * gdb_bfd.c (gdb_bfd_data): Add "st" parameter.
Tom> (gdb_bfd_init_data): New function.
Tom> (gdb_bfd_open, gdb_bfd_ref): Use gdb_bfd_init_data.
Tom> I'm checking this in now, since it is one of the blockers for the gdb 10
Tom> branch.
Apparently I never built this without -O0, because now I see an
uninitalized warning -- and worse, it points out a bug in the patch.
I'll fix it shortly. Sorry about this.
Tom
prev parent reply other threads:[~2020-09-08 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 18:57 Tom Tromey
2020-09-08 16:12 ` Tom Tromey
2020-09-08 16:24 ` Tom Tromey [this message]
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=878sdkkzig.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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).