Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month! Blinker 5.10 Online Reference - <b> tracing dos extender gpfs with bligpf</b> [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Tracing DOS extender GPFs with BLIGPF
 The BLIGPF utility reads a GPF dump from a DOS extended program and uses the
 MAP file created by Blinker at link time to trace the exact location of the
 GPF. This automates the manual analysis procedure described in the section
 entitled `General protection fault (GPF) analysis' in Chapter 5.

 The result of a GPF trace is simply information (including the symbol name)
 relating to the program code which was running when the GPF occurred, and is
 not necessarily the code responsible for the error, since GPFs can result
 from bad information being passed to good code.

 To use BLIGPF, start by creating a MAP file using the Blinker link script
 command MAP S,A, and make sure that this is in the same directory as the
 .EXE or .DLL causing the GPF. Run the program until the GPF occurs, and then
 immediately run BLIGPF from the DOS prompt to analyse the GPF dump while it
 is still on the screen. If the MAP file is not in the current directory then
 BLIGPF will be unable to find it, in which case you can specify the full
 path and file name of the MAP file on the BLIGPF command line.

Online resources provided by: --- NG 2 HTML conversion by Dave Pearson