[Bug binutils/22746] crash when running 32-bit objdump on corrupted file

2018-03-31 Thread jeremip11 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22746 Jeremi changed: What|Removed |Added CC||jeremip11 at gmail dot com -- You are

[Bug binutils/22746] crash when running 32-bit objdump on corrupted file

2018-01-25 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22746 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|amodra at

[Bug binutils/22746] crash when running 32-bit objdump on corrupted file

2018-01-25 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22746 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=38e64b0ecc7f4ee64a02514b8d532782ac057fa2 commit

[Bug binutils/22746] crash when running 32-bit objdump on corrupted file

2018-01-25 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22746 --- Comment #2 from Alan Modra --- Hmm, so i686-linux with --enable-64-bit-bfd reproduces the crash. It would be useful to report such configuration parameters when reporting bugs. -- You are receiving this mail because: You are on the CC

[Bug binutils/22746] crash when running 32-bit objdump on corrupted file

2018-01-25 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22746 Alan Modra changed: What|Removed |Added CC||amodra at gmail dot com --- Comment #1