[Bug binutils/25964] New: [nm] crash at vms_traverse_index at vms-lib.c:230

[dkcjd2000 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=25964

            Bug ID: 25964
           Summary: [nm] crash at vms_traverse_index at vms-lib.c:230
           Product: binutils
           Version: 2.34
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: dkcjd2000 at gmail dot com
  Target Milestone: ---

Created attachment 12522
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12522&action=edit
crash test case

Hello,
I'm currently developing a new fuzzing feature, and I found a crash in nm.

It crashed in vms_traverse_index at vms-lib.c:230

I built it with Ubuntu 16.04 with gcc 5.4.0, and the following command to build
nm from the source:
./configure --enable-targets=all ; make clean all -j 4; make install

You can reproduce the crash with the following command:
./nm <attached file>

The call stack of the crash is:
Program received signal SIGSEGV, Segmentation fault.
0x00000000006d5694 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:230
230     {
(gdb) bt
#0  0x00000000006d5694 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:230
#1  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
#2  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
#3  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
#4  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
#5  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
#6  0x00000000006d57b4 in vms_traverse_index (abfd=abfd@entry=0xb15290,
vbn=vbn@entry=1, cs=cs@entry=0x7fffffffdeb0) at vms-lib.c:288
...
#6806 0x00000000006d5ad1 in vms_lib_read_index (abfd=abfd@entry=0xb15290,
idx=idx@entry=0, nbrel=nbrel@entry=0x7fffffffdf3c) at vms-lib.c:414
#6807 0x00000000006d5d73 in _bfd_vms_lib_archive_p (abfd=0xb15290,
kind=kind@entry=vms_lib_alpha) at vms-lib.c:524
#6808 0x00000000006d7527 in _bfd_vms_lib_alpha_archive_p (abfd=<optimized out>)
at vms-lib.c:643
#6809 0x000000000040d6a9 in bfd_check_format_matches (abfd=abfd@entry=0xb15290,
format=format@entry=bfd_archive, matching=matching@entry=0x0)
    at format.c:328
#6810 0x000000000040dbf9 in bfd_check_format (abfd=abfd@entry=0xb15290,
format=format@entry=bfd_archive) at format.c:94
#6811 0x0000000000404679 in display_file (filename=0x7fffffffe5b0
"./report/crash6") at nm.c:1371
#6812 0x0000000000404d50 in main (argc=2, argv=0x7fffffffe318) at nm.c:1860

-- 
You are receiving this mail because:
You are on the CC list for the bug.