Date: Sun, 9 Oct 1994 13:42:58 -0400 (EDT)
From: Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Sender: Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Reply-To: Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Subject: symify summary
To: DJGPP Mailing List <djgpp AT sun DOT soe DOT clarkson DOT edu>


  Apparently none of the replies I got were CC'ed to the list since I got 
a letter from someone asking how symify works.
  Well, this is what it does:  if you compile a program with debugging 
info (-g) and it crashes, go32 will print out the stack trace on the 
screen (I'm sure you've all seen it).  Then you run symify with the name 
of the program that crashed ("symify badprog.out") and it'll turn the 
stack trace into line numbers.  Then you take the line numbers and find 
out what caused the crash.
  Now, I just tried this and it didn't work.  That's because you have to
run symify on the .out file instead of the .exe.  So what I did was run
a.exe then type "symify a.out" and it put glowing letters up by the stack
trace that said "_main+13".  I don't know what that means since my test
program was only 8 lines long.... 
  My test program was this:  (suggested by someone else)

int main() {

  char *c = 0;
 
  strcpy(*c,"Ooops!");
  printf("Shouldn't get here.");
  return 0;
}

  Maybe the _main+13 is the location of strcpy or something... the 
glowing letters look so encouraging...
  Can someone give me further help? :)
							Kim