Date: Sun, 1 Dec 1996 09:27:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Cc: DJGPP AT delorie DOT com
Subject: Re: v2 hex dump catching
In-Reply-To: <5F6B220689@fs2.mt.umist.ac.uk>
Message-Id: <Pine.SUN.3.91.961201092220.12293M-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 29 Nov 1996, A.Appleyard wrote:

> In v1 I had to put this in \autoexec.bat to tell djgpp to put the hex dump
> onto file T$GCCDBG so that I can call symify on it if the program run crashed.
> 
> set GO32=ansi driver d:/djgpp/contrib/libgrx/drivers/cirrus54.grn 2r1 noglob
> core t$gccdbg
> 
> What do I put in v2?

You can't, there's no such functionality in v2.  Your alternatives are:

	1) Run your program under another program which catches output.  
One such program is `redir' (from DJGPP); another is SCRIPT (from SimTel, 
see the FAQ).

	2) Hack the sources of the functions that prints the stack dump 
(in djlsr201.zip, on src/libc/go32/dpmiexcp.c) to write the info to a 
disk file.  You should be warned though that this might sometimes fail, 
if your program is so screwed up that it cannot use file I/O functions 
(such as `open').