Zero pain log extensions
André Timmermans (100) 655 posts |
When an application crashes with something like an abort on data transfer it would be nice to have an additional button in the wimp error box allowing to generate a report similar to a zero pain log. Also, for a crash in a BASIC application, it would be nice if zeropain could somehow retrieve the line number where the error occurs. Last time it took me quite some time reproduce and track down the cause of a crash in the BASIC module: a conversion of a pointer returned by a SWI into a BASIC string which failed because I forgot to check that the SWI did not end in error. |
Martin Avison (27) 1494 posts |
What version of BASIC were you using? Since v1.54 BASIC should report the ERL even for aborts in external code (eg SWI, CALL, etc). Unless you found an even more obscure way to create an abort! |
André Timmermans (100) 655 posts |
That is working fine, but in the case here there was no error reported because Zero pain was intercepting the null pointer exception. Took me a while to notice that I had a new zero pain report, and then I had a hard time figuring how to reproduce it again, I wasn’t even sure was if the problem was within the BASIC module itself our in program itself. I guess that at that point I should have disabled ZeroPain to see if the BASIC’s error handler would be able to cope with the error. |