This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

objdump segfault


If I use ar to add one archive to another, followed by a ranlib, an
objdump on the subsequent archive segfaults.  For example:

rm -f libpthread.a
x86_64-w64-mingw32-ar cru libpthread.a  .libs/libwinpthread.a
x86_64-w64-mingw32-ranlib libpthread.a

gdb --args x86_64-w64-mingw32-objdump -a libpthread.a

<...>

Program received signal SIGSEGV, Segmentation fault.
0x00000000004c0789 in objalloc_free ()
(gdb) bt
#0  0x00000000004c0789 in objalloc_free ()
#1  0x000000000044608d in bfd_hash_table_free ()
#2  0x0000000000443037 in _bfd_delete_bfd ()
#3  0x000000000044385c in bfd_close_all_done ()
#4  0x0000000000437f70 in archive_close_worker ()
#5  0x00000000004bf508 in htab_traverse_noresize ()
#6  0x0000000000437f43 in _bfd_archive_close_and_cleanup ()
#7  0x0000000000443091 in bfd_close ()
#8  0x000000000040805c in main ()
(gdb)


Thoughts?  This is with GNU objdump (rubenvb-4.8.0) 2.23.52.20130322
The binutils checkout that he did is unmodified.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]