Date: Tue, 31 Mar 1998 16:21:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
cc: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>, djgpp-workers AT delorie DOT com
Subject: Re: Auto-symified traceback
In-Reply-To: <3520DBE2.192F@rug.ac.be>
Message-ID: <Pine.SUN.3.91.980331161737.24624D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 31 Mar 1998, Vik Heyndrickx wrote:

> Eli Zaretskii wrote:
> > You mean, create a `core' file?  I don't know.  Opinions, anyone?
> 
> How do users get this traceback as input to symify?

	symify -i core program-name

> The only method that
> I know of is "redir"-ing the traceback into a file (or copy it by hand
> ;-).

That's why I understand George suggested to modify the traceback function 
to print to the screen *and* write to a file at the same time.

> Except in an exceptional occasion, the traceback alone doesn't tell
> the user or author much what went wrong.

OTOH, it doesn't seem to hurt, either.

> reason, then write to stderr instead). I wouldn't duplicate that
> traceback on the screen, just a "proper" abort message and info to the
> user where the, ahum ahum, "core" image was written to.

Something like "Abort!---core dumped"?  It's also possible.