Date: Mon, 3 Nov 1997 17:37:42 -0800 (PST)
Message-Id: <199711040137.RAA10945@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: objdump 2.7 crash
Precedence: bulk

The objdump from Binutils 2.7 crashed on me today. Here's the specifics:

I have a file "libc_g.a", which is the libc, patched somewhat, built with
stabs debugging. (I have my GCC patched for stabs and added `-g' to the
response file when building libc.)  I ran:
objdump --debugging libc_g.a

It crashed with SIGSEGV. I then rebuilt objdump with `-gcoff' (so symify
would work) and obtained a traceback, which I include below. I'm quite sure
this is not related to the usual stack limitation, since (a) the ESP in the
traceback was reasonable, and (b) the problem persisted even when
objdump.exe was stubedited to a 4MB stack.

Okay, the big question: Does it still happen with objdump 2.8.1?  I don't
know. I only have 2.7, and I don't have FTP to get 2.8.1 and find out. If
anybody reproduces this, or investigates it further, I'd like to know. I'm
not sure if this is a GNU bug or one specific to DJGPP, and I also don't
know if perhaps it's been fixed.

Traceback from the crash:
Exiting due to signal SIGSEGV
General Protection Fault at eip=00009d81
eax=656e6771 ebx=00030410 ecx=00000000 edx=00000003 esi=00000074 edi=00074fc4
ebp=000b4e10 esp=000b4e08 program=C:\DJGPP\GNU\BINUTL-2.7\BINUTILS\OBJDUMP.EXE
cs: sel=00a7  base=80bfc000  limit=000dffff
ds: sel=00af  base=80bfc000  limit=000dffff
es: sel=00af  base=80bfc000  limit=000dffff
fs: sel=0087  base=0000f190  limit=0000ffff
gs: sel=00bf  base=00000000  limit=ffffffff
ss: sel=00af  base=80bfc000  limit=000dffff

Call frame traceback EIPs:
  0x00009d81 _debug_add_to_namespace+65, line 610 of debug.c
  0x0000b576 _debug_name_type+182, line 1976 of debug.c
  0x0000f815 _parse_stab_string+2273, line 957 of stabs.c
  0x0000ee85 _parse_stab+1481, line 616 of stabs.c
  0x00009701 _read_section_stabs_debugging_info+905, line 206 of rddbg.c
  0x00009271 _read_debugging_info+57, line 57 of rddbg.c
  0x000047e9 _display_bfd+505, line 1474 of objdump.c
  0x00004935 _display_file+185, line 1527 of objdump.c
  0x000061b4 _main+1728, line 2199 of objdump.c
  0x000599e2 ___crt1_startup+490


Nate Eldredge
eldredge AT ap DOT net