From: "John M. Aldrich" Newsgroups: comp.os.msdos.djgpp Subject: Re: v2 hex dump catching Date: Fri, 29 Nov 1996 11:57:29 -0800 Organization: Three pounds of chaos and a pinch of salt Lines: 41 Message-ID: <329F4029.35AC@cs.com> References: <5F6B220689 AT fs2 DOT mt DOT umist DOT ac DOT uk> Reply-To: fighteer AT cs DOT com NNTP-Posting-Host: ppp211.cs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "A.Appleyard" DJ-Gateway: from newsgroup comp.os.msdos.djgpp 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? v2 executables dump the stack trace directly to stderr. The old go32 options don't work anymore because v2 doesn't use go32 (except as an intermediary for unstubbed images). There are two ways to do what you need: 1) When the crash traceback is on the screen, type "symify -o " to copy the symified data to a file. 2) If your program uses graphics or in some other way makes it impossible to see the traceback, use 'redir' to redirect stderr to a file, and then run stubify on that file, like so: redir -e t$gccdbg symify -i t$gccdbg This, IMHO, is much easier than fooling around with environment variables. BTW, I noticed 'noglob' in your go32 environment variable. This is also no longer done in the environment, but is established individually by each and every program. To see how, look up __crt0_glob_function() in the libc docs. Good luck! -- --------------------------------------------------------------------- | John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com | | Proud owner of what might one | http://www.cs.com/fighteer | | day be a spectacular MUD... | Plan: To make Bill Gates suffer | ---------------------------------------------------------------------