X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
Date:	Sun, 07 Apr 2002 18:18:51 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<3405-Sun07Apr2002181850+0300-eliz@is.elta.co.il>
X-Mailer:	emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<3CB045A9.F1144A96@yahoo.com> (message from CBFalconer on Sun, 07
	Apr 2002 13:57:44 GMT)
Subject:	Re: Exiting due to signal SIGSEGV
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1020407142628 DOT 22519C-100000 AT is> <3CB045A9 DOT F1144A96 AT yahoo DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: CBFalconer <cbfalconer AT yahoo DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 07 Apr 2002 13:57:44 GMT
> 
> Is there any special reason that addr2line is not incorporated in
> symify?  Why have the user need to transcribe hex addresses from
> the screen?

I don't understand: SYMIFY does translate hex addresses into human
readable file name and line number information.  addr2line does the
same, except that its UI is different.

Perhaps you meant why isn't the equivalent of SYMIFY part of the
standard library exit code?

If you want a version of SYMIFY that knows about debug formats other
than COFF (like stabs or DWARF2), like addr2line does, you can use
bfdsymify.exe from the GDB 5.1.1 distribution.  bfdsymify has the same
UI as SYMIFY.

> Another convenience: At least with 4dos an environment variable
> CMDLINE is left, so symify without parameters could use that by
> default.

If you want to use CMDLINE to get the name of the program, there's no
need for that: the crash message includes the full path to the
program's executable.  This is better than CMDLINE, since the latter
doesn't tell where to look for the .exe file.

- Raw text -