OpenEuphoria

Re: How come: crash/no crash?

• Posted by Brian Broker <brian_broker at yahoo.com> Dec 29, 2005
• 442 views

C Bouzy wrote:
> 
> Brian Broker wrote:
> 
> > It's certainly not fair to blame any OS for programming mistakes.  However,
> > it may not be a programming mistake at all.  The system that's crashing may
> > have DEP enabled and that will generate a machine-level exception by just
> > running
> > Euphoria's own Win32 demo programs.
> > 
> > DEP is Data Execution Prevention.  To check the settings, open the System
> > control
> > panel, click the Advanced tab, click Performance settings button, click Data
> > Execution Prevention tab.  If you don't want Euphoria to crash, you should
> > either
> > have the first radio selected (turn on DEP for essential Windows programs
> > and
> > services only) or you will need to create an exception for your program if
> > the
> > second radio is selected (turn on DEP for all programs and services except
> > those
> > I select).
> > 
> > I recently ran into this issue again and it was nearly impossible to debug.
> > 
> > -- Brian
> 
> Disabling DEP is not a good idea, your app should run with it on. DEP is
> used to prevent viruses from running malicious code from memory locations,
> and almost every XP computer with Service Pack 2 installed will have this
> enabled by default. You cannot tell every user who wants to run your
> app to disable DEP.
> 
> 
> ----If you continue to do what you have always done,
> you will get what you have always gotten.----

I'm not sure if my last message was submitted or was closed via accidental
keystroke so forgive me if I sound redundant.

I searched the list and found that I mentioned that Windows *software* DEP does
not affect Euphoria Windows programs.  However, my latest job requires that I
develop running on x64 systems running W2k3 Server.  My last dev box must have
had hardware DEP enabled because I had to disable it to get Eu windows programs
working.

If your user has processor-level DEP capabilities, it *might* cause a
machine-level exception if these *strong* settings are enabled.

-- Brian