Re: EXW crash
- Posted by Robert Craig <rds at RapidEuphoria.com> Dec 22, 2002
- 445 views
Martin Stachon writes: > Sometimes, exw.exe crashes because of programmers error, > like invalid pointer etc. > This window is shown : > > Application Error: C:\EUPHORIA\BIN\EXW.EXE [X] > ----------------------------------------------- > The instruction at xxxxxxxx referenced memory at ffffffff. > The memory could not be read from. > > Click OK to terminate the application. > > [OK] > > The error message is not from Windows, but from some > C runtime libraries linked in EXW.EXE. Do you think it would > be possible for exw to add its own handler for this and show > where the crash happened and do some cleanup? Excellent idea! I should have tried this long ago. Somehow I thought it wasn't possible. I set up an exception handler under Watcom/DOS a long time ago, and it didn't work at all, but I never tried it with Windows. I think it will probably work with Linux and FreeBSD too. As a test, I just added a handler for both segmentation violation and illegal instruction to exw, and it worked. I got a nice Euphoria traceback pointing to: poke(0, 999), where before I would have seen a useless message like the one you show above. When I think of all the hours people have spent debugging these sorts of errors ... Yikes! (2.4 alpha-test should be available in a few weeks.) Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com