Mail Archives: djgpp/1996/05/17/19:20:12
Xref: | news2.mv.net comp.os.msdos.djgpp:3969
|
From: | Broeker AT PROBLEM_WITH_INEWS_DOMAIN_FILE (Hans-Bernhard Broeker)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: What is symify? Is this in the V2 FAQ?
|
Date: | 17 May 1996 17:22:25 GMT
|
Organization: | RWTH -Aachen / Rechnerbetrieb Informatik
|
Lines: | 18
|
Message-ID: | <4nickh$fb7@news.rwth-aachen.de>
|
References: | <4nec8d$bmj AT freenet-news DOT carleton DOT ca>
|
NNTP-Posting-Host: | axpcl8.physik.rwth-aachen.de
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Paul Derbyshire (ao950 AT FreeNet DOT Carleton DOT CA) wrote:
> What is symify? It keeps getting mentioned here. Or is this in the V2 faq?
> (I still have only the v1 faq.)
Bad choice. Go and get the V2 FAQ, definitely.
As to symify, that's a small program that can decode the traceback you
get when your program crashes at run time into function names and line
numbers, provided you compiled your program using the '-g' switch.
Just call 'symify prog' with the traceback report still on the screen,
it will rewrite the information in place. (A note: you *must* have
compiled with "gcc -o prog", *not* with "gcc -o prog.exe" for this to
work. It needs the file "prog", not "prog.exe"). In a nutshell, it's a
last-resort debugger.
Hans-Bernhard Broeker (Aachen, Germany)
- Raw text -