diff options
author | Alan Modra <amodra@gmail.com> | 2017-09-15 10:22:13 +0930 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2017-09-15 10:36:40 +0930 |
commit | 21d0a60620b306d6471ddedff04ac23912596cc6 (patch) | |
tree | 3f6bacef41f452a3947e289c61d99a2d379139e9 /ChangeLog | |
parent | cc3e190059e6c817203049a52c8bc4b37b58ce74 (diff) | |
download | gdb-21d0a60620b306d6471ddedff04ac23912596cc6.zip gdb-21d0a60620b306d6471ddedff04ac23912596cc6.tar.gz gdb-21d0a60620b306d6471ddedff04ac23912596cc6.tar.bz2 |
Error when 32-bit ar tries to handle 4G or larger files
We used to silently truncate the size returned by stat() to 32 bits.
While it is possible to make binutils handle a 64-bit off_t on a
32-bit host, to me the effort needed doesn't seem worth the benefit.
Instead, error if we truncate the size. I've written the test the way
I have to avoid a signed/unsigned warning.
PR 22116
* archive.c (bfd_ar_hdr_from_filesystem): Detect when status.st_size
overflows bfd_size_type.
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions