From: fesenko AT pacific DOT net DOT sg (Victor)
Newsgroups: comp.os.msdos.djgpp
Subject: Debugging after program crashes
Date: Wed, 23 Sep 1998 23:40:19 GMT
Organization: Subscriber of Pacific Internet, Singapore
Lines: 17
Message-ID: <3609854d.114750420@news>
NNTP-Posting-Host: dyn65ppp209.pacific.net.sg
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I've read the chapter in the new FAQ that discusses the subject. It is
very insightful (thanks to Eli for that).
I have a situation where the first (or is it called last?) entry in
the traceback list shows the function which is not called from the
previous function at all. Which leads to a suggestion that the RAM in
that place was corrupted by another process. And the problem is that
the crash can't be easily reproduced.
The good idea would be to have a disassembly in the places indicated
by the last 2-3 tracebacks, maybe few commands before and after the
exact traceback location.
So the question is - does anyone know how to hook exception (SIGSEGV
or page fault) for the purpose of saving to a file the memory contents
from around the locations indicated by traceback list?
Any ideas appreciated.

Victor Fesenko.
fesenko AT pacific DOT net DOT sg