From: Nick Alcock <nick.alcock@oracle.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: ctf segfaults
Date: Fri, 24 Mar 2023 13:35:49 +0000 [thread overview]
Message-ID: <87lejmmfuy.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZBb3JpbiFebpIfHc@squeak.grove.modra.org> (Alan Modra via Binutils's message of "Sun, 19 Mar 2023 22:21:02 +1030")
On 19 Mar 2023, Alan Modra via Binutils uttered the following:
> PR 30228
> PR 30229
> * ctf-open.c (ctf_bufopen_internal): Check for NULL cts_data.
> * ctf-archive.c (ctf_arc_bufpreamble, ctf_arc_bufopen): Likewise.
Thanks! (These were fuzzed archves, right? Real archives should never
end up with, what is that, a zero-length types section?)
prev parent reply other threads:[~2023-03-24 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 11:51 Alan Modra
2023-03-24 13:35 ` Nick Alcock [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=87lejmmfuy.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=amodra@gmail.com \
--cc=binutils@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).