1. exe.exw error
- Posted by sixs at ida.net Oct 15, 2003
- 474 views
This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C39280.64F93A30 charset="iso-8859-1" I get this message "The instruction at "or77f58d2c" referenced memory at = "ox8001ba7" The memory could not be written Click OK to terminate the program" Jvandal ------=_NextPart_000_0007_01C39280.64F93A30 charset="iso-8859-1" <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I get this message "The instruction at = "or77f58d2c"=20 referenced memory at "ox8001ba7" The memory could not be = written</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Click OK to terminate the = program"</FONT></DIV> ------=_NextPart_000_0007_01C39280.64F93A30--
2. Re: exe.exw error
- Posted by Robert Craig <rds at RapidEuphoria.com> Oct 15, 2003
- 442 views
sixs at ida.net wrote: > I get this message "The instruction at "or77f58d2c" referenced memory at > "ox8001ba7" The memory could not be written > Click OK to terminate the program" This is usually due to your program poking some data into an illegal memory location, or passing a bad value to a C routine. It's rarely a bug in exw.exe itself. If you are still using Euphoria 2.3 or earlier, you should install 2.4. It can handle most machine-level exceptions like this one. It will pinpoint the Euphoria statement that caused the error, and give you a ex.err file. Pre-2.4 Euphoria would just crash with a cryptic operating system message like the one you are reporting, and no ex.err. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com