Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » I keep getting the same "cannot open exe for writing" error...
Re: I keep getting the same "cannot open exe for writing" error... [message #50623 is a reply to message #50621] Tue, 27 November 2018 10:07 Go to previous messageGo to previous message
peterh is currently offline  peterh
Messages: 46
Registered: November 2018
Location: Germany
Member
Thank you!
So this is in nightly build tomorrow?

I am going to test and report in the evening, when I am at home.
Dayover I am at Job and look occasionally into the forum.
My Job is not programming, but industrial electronics hardware.

My idea is this:

In normal cases termination should be quicker than some 100 milliseconds.
Only if there are problems like pending IO it would last longer.
I do not know if in this cases Windows waits or if it terminates the process in the hard way, leaving open serial ports, USB devices and Files behind. Wink

However the timeout in WaitForSingleObject() must have a meaning and nobody knows how the next version of Windows or other versions will handle this.
So, if a timeout happens there must be an unusual problem and only the user/programmer can know for the reason.

It is then questionable wether the termination would succeed and the user should be asked, when a timeout happens if he wants to wait, instead of closing the process-handle, possibly unsuccessful.
Inbetween he/she could use other system-tools to debug or ignore the problem and restart the IDE and possibly chooses to reboot afterwards.

We use hardware testprograms here.
Some of the devices we test are defective and have unforseeable problems. This is, why we test. Wink
We connect potentially defective devices to the USB Port and disconnect them, semiautomatically some hundreds a day.
I have often seen USB devices vanish after a crash and in this case there is no other choice than to reboot after such an event.
So if such a situation is encountered while debugging the test program, the debugger must leave the decision about closing a process handle after timeout to the debuggers user.

[Updated on: Tue, 27 November 2018 13:17]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: error: expected unqualified-id before '=' token
Next Topic: clang or MinGW
Goto Forum:
  


Current Time: Sun Oct 25 05:40:06 CET 2020

Total time taken to generate the page: 0.01603 seconds