Miguel Angel,
> Thank's to Jose F. Gimenez, we found the problem.
It's always a pleasure to help when I can ;-)
> Them problem resides on
>
> #if defined(HB_OS_WIN_32)
> if( s_bUnInitOle )
> {
> OleUninitialize();
> }
> #endif
>
> at HB_EXPORT int hb_vmQuit( void )
>
> it can be called in this point, because generate a message.
> The GPF always existed and has only been caught by the last CVS
>
> Any ideas to solution ?
The problem arises when a program leaves an ActiveX running when exiting,
and this ActiveX tries to access any memory block or any other resource
which belongs to the program (i.e. a string, a safearray, an image, etc.
passed to the ActiveX). Moreover, there are even buggy OCX that stay running
after an explicit 'release', that causes a GPF as well.
IMO, the solution is to move up the call to OleUninitialize() in hb_vmQuit()
just after executing exit procedures. It could be just before or after the
call to hb_vmDebuggerExit()
Regards,
Jose F. Gimenez
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
