
Click above to get retro games delivered to your door ever month!
X-Hacker.org- CA-Clipper/ExoSpace 1.0g - <b>protection fault</b>
[<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
Protection Fault
------------------------------------------------------------------------------
If your CA-Clipper/ExoSpace application terminates with a General
Protection Fault (Error 35), look at the selector that
CA-Clipper/ExoSpace reports as the location where the problem occurred.
The selector is the number printed before the colon. For example, in
the error message below, the fault is reported as occurring "at
016F:0022." In this case, the selector is 016F:
Error [35]: General Protection Fault in
MYAPP.EXE at 016F:0022
code=0000 ss=07FF ds=07FF es=0000
ax=0004 bx=0016 cx=0000 dx=0000
sp=7B50 bp=7B56 si=0000 di=0001
Unless your application is running under DPMI (e.g., in a Microsoft
Windows DOS box), a selector value less than 200h indicates an error in
the CA-Clipper/ExoSpace code. Selector values greater than 200h
indicate a problem in the application code--either in a third-party
library, or other C or Assembler code. The error message shown above
was generated by a NULL pointer error in a third-party library or other
C or Assembler code.
When you link an application, you can generate a .MAP file using the MAP
command in the link script. Unless your application is running under
DPMI, you can find out which module and/or routine is at fault by
finding the selector number and closest offset in the map file.
Another way to determine where the problem is occurring is to use the
CA-Clipper debugger to trace up to the point where the problem occurs.
Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson