>> Can this be somehow fixed to be fool-proof on the app level? >> >> It's still not a good thing to let anything on .prg level to >> cause GPFs. >> > > This is exactly for what I changed QApplication() protocol.
I'm not sure I understand, the GPF was reported using the most recent revision. Are you saying the possibility of the mentioned GPF is now fixed? > Just do not have any init/exit procedures initiating QApplication at all > in prg code. It is done automatically at cpp level. > > This is because we do not have control over which init procedure > will execute first. Okay, I got that part. All I'm saying is that it's still a sign of .prg code (whatever .prg code) is still causing GPF for some reason: --- Unrecoverable error 6005: Exception SIGSEGV at address 0x10004 Called from QT_QAPPLICATION_EXEC(0) Called from QAPPLICATION:EXEC(0) in ../../../TQApplication.prg Called from MAIN(195) in ./source/us_editor_new.prg br...@notebook:~/marinas-ide/editor/source$ --- Couldn't there be an RTE issued instead? Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
