RE: EXW crash
- Posted by Andy Serpa <ac at onehorseshy.com> Dec 22, 2002
- 407 views
> 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.) > Most errors I get involving .dlls cause a pop-up "EXW.EXE has caused an error in such-and-such." Not sure it ever makes its way back to the interpreter. Any chance of catching those? They can be very hard to pin down...