Message-ID: <3DAD80B7.98C390C1@cyberoptics.com>
Date: Wed, 16 Oct 2002 10:07:35 -0500
From: Eric Rudd <rudd AT cyberoptics DOT com>
Organization: CyberOptics
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: symify problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 56
NNTP-Posting-Host: 65.214.97.102
X-Trace: 1034780859 reader2.ash.ops.us.uu.net 934 65.214.97.102
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I have used symify for many years without a problem, but lately I have
been having problems getting line numbers in a traceback.  For example,
here is a little test program:

   #include <signal.h>

   void sub(void) {
      raise(SIGABRT);
   }

   int main(void) {
      sub();
      return 0;
   }

I compile it using gcc v3.2, and "as" v.2.13:

   C:\temp>gcc -g test.c -o test.exe

I then run it and "symify" the dump:

C:\temp>test
Exiting due to signal SIGABRT
Raised at eip=00003eae
eax=0008d84c ebx=00000120 ecx=00000000 edx=0000033f esi=00000054
edi=0000d960
ebp=0008d8f8 esp=0008d848 program=C:\TEMP\TEST.EXE
cs: sel=00a7  base=83856000  limit=0009ffff
ds: sel=00af  base=83856000  limit=0009ffff
es: sel=00af  base=83856000  limit=0009ffff
fs: sel=0087  base=0001a870  limit=0000ffff
gs: sel=00bf  base=00000000  limit=0010ffff
ss: sel=00af  base=83856000  limit=0009ffff
App stack: [0008d960..0000d960]  Exceptn stack: [0000d8c0..0000b980]

Call frame traceback EIPs:
  0x00003dd4 ___djgpp_traceback_exit+48
  0x00003eae _raise+90
  0x00001713 _sub+19
  0x0000172d _main+21
  0x00002f88 ___crt1_startup+176

C:\temp>symify -o test.log test.exe

As you can see, symify gives me the subroutine names and offsets, but
no line numbers.  I don't know what I'm doing wrong -- this used to
work.  Is this a new problem that was introduced in gcc v3.2?  I'm
using a symify.exe dated 2001-12-24 (in the latest DJDEV203).  I dimly
recall that there was some way of getting an annotated assembly listing
that included the offsets of the line numbers, but either I can't
remember how to do that, or it doesn't work anymore. What should I do
next to isolate this problem?

-Eric Rudd
rudd AT cyberoptics DOT com