>Ramana Kumar escribi=F3:
>
>> if you have the latest version (4.9.4.0) then while you are executing
your code, the dev-c++ window should still be accessible, although, in some
older versions, this was not possible i believe.
>> also, in response to the fact that someone could compile while a
compiled executable was running, i would be quite scared also. but please
note, i find that dev-c++ starts to comiple in this case and runs the
makefile compiler linker etc... but eventually gives the "permission
denied" message instead of "compilation succesful" and no new executable is
produced.
>
>Exactly as happen, dev is accesible, and if I try to compile permission
denied (more exactly nothing at all or error access module or something
like that, I don't remember, it happened a couple of times in the past, and
I have never again that mistake)
It may be that one of the following is happening:
1. Your program never fully exited. Windows closed, and it doesn't show up
on the taskbar, but it still has some thread running. If that is the case,
you won't be able to write over it (permission denied).
2. If you ran it in the debugger, make sure that when you are finished with
your program, you exit debug mode (or the debugger, if you are using a
standalone debugger like Insight). If your program is finished, but the
debugger is still running, the debugger will hold your program's executable
image open and you will get a permission denied error.
Mac
-
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
re...@no... / \ (To join the campaign, simply use
this in your signature.)
=20
|
