delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2002/10/21/08:00:41

From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: symify problem
Date: 21 Oct 2002 11:24:25 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 16
Message-ID: <ap0o59$pbd$1@antares.lu.erisoft.se>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1021020075023 DOT 7066A-100000 AT is>
NNTP-Posting-Host: lws256.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:

: On Thu, 17 Oct 2002, Charles Sandmann wrote:

: > Should symify check the debug symbol type and warn if it's not coff
: > and it can't find bfdsymify?

: I'm not sure.  SYMIFY should not use the screen estate for anything that 
: is not essential.  We should not risk scrolling parts of the crash 
: message off the screen, IMHO.

: Perhaps a simple "(no COFF debug info)" somewhere would suffice, assuming 
: we can find a place that doesn't use another screen line.

The line "Call frame traceback EIPs:" could become "Call frame
traceback EIPs, N.B. no coff debug information:".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019