Message-ID: <3DB28375.225AD32B@yahoo.com>
From: CBFalconer <cbfalconer AT yahoo DOT com>
Organization: Ched Research
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: symify problem
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1021020075023 DOT 7066A-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 22
Date: Sun, 20 Oct 2002 10:32:08 GMT
NNTP-Posting-Host: 12.90.168.183
X-Complaints-To: abuse AT worldnet DOT att DOT net
X-Trace: bgtnsc05-news.ops.worldnet.att.net 1035109928 12.90.168.183 (Sun, 20 Oct 2002 10:32:08 GMT)
NNTP-Posting-Date: Sun, 20 Oct 2002 10:32:08 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii 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.

Hasn't symify already scrolled one line?  If it is mis-called it
already scrolls at least two more lines off.    Seems to me there
has to be room for something.

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!