From: "Martin Liška" <mliska@suse.cz>
To: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: pe_ILF_object_p and bfd_check_format_matches
Date: Thu, 13 Apr 2023 11:55:10 +0200 [thread overview]
Message-ID: <e8047f42-0358-dc98-4949-6b92a4dbd8e5@suse.cz> (raw)
In-Reply-To: <ZDdvur4hs0gJxEZp@squeak.grove.modra.org>
On 4/13/23 04:58, Alan Modra via Binutils wrote:
> |The last patch wasn't quite correct.|
Heh, I've just noticed that this change caused a crash when ar is called for ~150 files:
==27734== Invalid read of size 4
==27734== at 0x4D576DD: ftello (in /usr/lib64/libc.so.6)
==27734== by 0x4958E18: close_one (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x495F2F4: bfd_open_file (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x4B86557: bfd_plugin_open_input (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x4B8674F: try_load_plugin (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x4B86A5B: bfd_plugin_object_p.lto_priv.0 (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x49626EA: bfd_check_format_matches (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x4963016: _bfd_write_archive_contents (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x4968DD5: bfd_close (in /usr/lib64/libbfd-2.40.50.20230412-797.so)
==27734== by 0x10E9BB: write_archive (in /usr/bin/ar)
==27734== by 0x1103DD: main (in /usr/bin/ar)
==27734== Address 0x0 is not stack'd, malloc'd or (recently) free'd
Martin
next prev parent reply other threads:[~2023-04-13 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 1:32 Alan Modra
2023-04-13 2:58 ` Alan Modra
2023-04-13 9:55 ` Martin Liška [this message]
2023-04-13 10:58 ` Alan Modra
2023-04-13 12:53 ` Martin Liška
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=e8047f42-0358-dc98-4949-6b92a4dbd8e5@suse.cz \
--to=mliska@suse.cz \
--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).