User forums > General (but related to Code::Blocks)

windows 7 "permission denied" problem

(1/7) > >>

websnake:
when i compile any program it executes 2 or 3 times fine but after that C::B gives me error when i compile it again it gives me error....

ld.exe||cannot open output file C:\Users\username\Documents\Codeblocks\del it .exe Permission denied

and when i restart C::B then it works fine but again after compiling program 1 or 2 time again it says "permission denied".

i am facing this problem from past few days.

more info:-
OS - window 7 ultimate
C::B - SVN 7075
status - i don't have girlfriend  :(

MortenMacFly:

--- Quote from: websnake on July 26, 2011, 09:43:55 pm ---i am facing this problem from past few days.

--- End quote ---
This sounds to me like either a non-stopping application (i.e. it remains in memory after closing) or an issue with an AntiVirus (/defense) software that does not free it's handle to the executable.

You can try:
- inspect the running processes in your task manager to see if the app closed properly
- disable your AV / defense software temporarily, see if the problem is gone
- use a tool like process explorer (from sysinternals), search for the handle of your application and see which (other) process gained a handle to it

Note that this is 99.9% not an issue with Code::Blocks, but with the system.

websnake:
i tried first two methods i turned my antivirus off and also checked process list but i found nothing.

but i noticed that after executing the program and after when i get permission denied error when i wait 1 or 2 minutes i can execute it again without any error.

i will try process explorer. may be i am missing something :? .

ouch:
it could also be a loop running in your program. just because you pushed that x to close it doesn't mean your app kills it's self mid process.

MortenMacFly:

--- Quote from: ouch on July 26, 2011, 10:32:59 pm ---it could also be a loop running in your program. just because you pushed that x to close it doesn't mean your app kills it's self mid process.

--- End quote ---
Yes, but then it should appear in the task manager which isn't the case:

--- Quote from: MortenMacFly on July 26, 2011, 09:55:34 pm ---- inspect the running processes in your task manager to see if the app closed properly

--- End quote ---

--- Quote from: websnake on July 26, 2011, 10:27:59 pm ---i tried first two methods i turned my antivirus off and also checked process list but i found nothing.

--- End quote ---

Navigation

[0] Message Index

[#] Next page