WV>What I (under Windows) do is the following. I start the
WV>debugger and let the debugger run the app. When an
WV>exception occurs, the debugger is invoked in assembler
WV>mode, showing the faulty instruction. Since I don't do
WV>assembler (much), I alter the invalid pointer
WV>(segment:offset values, replacing them with valid values
WV>(usually ds:0 or a known and sacrificable variable)), and
WV>then stepping through the asm until I hit source code.
WV>It works with Turbo debugger (Windows), but not with CodeView (also windows)
WV>because it won't let you continue after an exception 13. So
WV>the possibility is that it might work with OS/2 also. It
WV>surely is the fastest method I know (at the moment)

An even faster way under TD is to look at the stack window.  It lists
all the function calls, and will let you see the offending source line
instantly.

Rob.
___
 X SLMR 2.1a X He's dead Jim. You get his tricorder, I'll get his wallet

--- Maximus/2 2.01wb