Message-Id:	<199804010030.BAA24868@sable.ox.ac.uk>
Comments:	Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From:	George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To:	Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Date:	Wed, 1 Apr 1998 01:29:24 +0000
MIME-Version:	1.0
Subject:	Re: Auto-symified traceback
Reply-to:	george DOT foot AT merton DOT oxford DOT ac DOT uk
CC:	djgpp-workers AT delorie DOT com

On 31 Mar 98 at 15:54, Martin Stromberg wrote:

> As for core files, why not? In Unix you can set the maximum core size with
> limit; perhaps an environment variable or an entry in DJGPP.ENV could be 
> used, and when it's zero or undefined, no core files would be created?

I think the average DOS user would be very annoyed at having large
files dumped to disk.  IMHO proper core file support (if any) should
be an optional extra, possibly enabled by the environment or the
programmer.  Unless GDB can read them I don't expect many people
would be interested in it though.

If GDB support isn't feasible, people can simply use their own signal 
handlers to generate their core files and use a custom debugger to 
browse them.

-- 
george DOT foot AT merton DOT ox DOT ac DOT uk
 
> > will know to send the traceback back to the author.
> 
> Try counting the number of messages on c.o.m.d where some of us
> explain how to get a symified traceback.  That alone could be a good
> reason to include such functionality, don't you think?

Hmm.  Would it not be almost equally effective to add a line after 
the traceback telling the user what to do with it?  Something like:

: ...
:   0x0001d5fb
:   0x000160dc
: 
: Run "symify c:/prog/file.exe" for more information.

The program name can be filled in automatically.  This doesn't help 
end users any more of course; if anything it might confuse them.  The 
message could be changable by the programmer, with something like the 
above being the default.
-- 
george DOT foot AT merton DOT ox DOT ac DOT uk

- Raw text -