...or is it Harbour that is telling Windows that a GPF occurred? If
so, we should make this optional and just allow the EXE to exit.
Hi Viktor,
What would also be great would be if you could optionally (eg.
_SET_FORCE_FATER_TERMINATION) force the app to close instead of being
held open by the O/S GPF alert message. For example, a server
application that runs into a GPF, is held open/running since Windows
attempts to display the GPF window - If Harbour could force the app
to terminate (again, as an option), this would be very helpful.
Best regards,
Randy.
At 02:34 PM 9/23/2008, you wrote:
Hi Randy,
Hi all,
I suggest the following changes to EXTAP.C:
1. The log should be closed BEFORE any alert messages are displayed.
True and thanks, I'll commit this ASAP.
2. There needs to be a way to suppress any alert messages (ie.
create log and exit) for applications that do not require user
activity (eg. server programs).
How about making GPF a simple internal error call?
[ I'd personally avoid any MessageBox() calls from any
Harbour core or contrib code. ]
To suppress .log file, I'll modify the code to explicitly
not try to create a log file if the _SET_HBOUTLOG filename
is empty, but this probably works even now.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
