From: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
To: DJGPP AT SUN DOT SOE DOT CLARKSON DOT EDU
Date: Tue, 4 Apr 1995 15:08:09 GMT
Subject: A small macro that saves a bit of finger wear in debugging progs

(1) I have this line in my AUTOEXEC.BAT :-

set GO32=ansi driver c:/djgpp/contrib/libgrx/drivers/cirrus54.grn 2r1 noglob
core t$gccdbg

(as one line). Thus if the program crashes, the hex stack dump goes into the
current directory's file T$GCCDBG.

(2) To my djgpp I added a file DJGPP\BIN\GCCEXP.BAT, which contains:-
symify -i t$gccdbg %1 > t$gccexp

  Thus if the program was compiled and assembled and linked using the `-g'
argument, if the program fails, typing `GCCEXP xxx' (where xxx is the name
(with suffix) of the <binary object> form of the program that failed) will
write to the local directory's file T$GCCEXP a copy of <all of> the local
directory's file T$GCCDBG with inserted readable commentary saying what lines
of what subroutines at each current call level the failure occurred in.
  All this writing to T$GCCDBG and T$GCCEXP is appended, so these two files in
each directory will keep accumulating rhubarb unless you delete them after
each use.