Jaime Escobal Mc Evoy
jaime....@sipsa.com.pe
Lima, Peru
With Blinker 4 comes an utility program called BLIGPF.EXE. If you run this
utility right after your program halts with a GPF. At command prompt type
BLIGPF and it will return the name of the offending symbol, the one that
caused the GPF. This could be a function you designed, a function in a
library you´re using that is not protected mode compatible or ... .
In order to BLIGPF.EXE work properly you have to comply to the following
conditions :
1 - When you link, you have to generate a .MAP file (include MAP S,A as the
last line of your link script)
2 - Place this .MAP file in your directory application.
Hope this helps.
Best regards,
Miguel Oliveira
Jaime Escobal McEvoy wrote in message
<35778e0b...@news.unired.net.pe>...
Jaime Escobal McEvoy wrote:
> Hi There,
> Can anybody tell me how to analyze that blinker 4.1 full screen of
> data you get with the BLX286 : 1313 : exception error 0D : general
> protection fault error? Thanks in advance for any help
>
> Jaime Escobal Mc Evoy
> jaime....@sipsa.com.pe
> Lima, Peru
What libraries are you using? Try changing the orders they are linked.
I just resolved the same problem using Clipper 5.3, Blinker 3.3, and DGe
5.0c. It turned out that DGe files had to be linked last.
Use a program called BLIGPF to analyse the error.
A map file has to be created when linking.
HTH
--
Steve Quinn
BRUTE Computer Services - Australia
squinn@brutecom~com.au <--- ANTI-SPAM Replace ~ with .
http://www.brutecom.com.au
Walter Joseph <wjco...@mail.bulkley.net> wrote in article
<357E0412...@mail.bulkley.net>...