• realhet (13/13) Mar 01 2023 Hello,
• Imperatorn (3/16) Mar 03 2023 We don't know what you mean by your definition of safe
• realhet (5/7) Mar 03 2023 For example killing ldc2.exe while it writes some cached temp

realhet <real_het hotmail.com> writes:

Hello,

Is it safe to kill an ongoing LDC2 process on Windows?

My situation is this:
- I launch 8 LDC2 compilation command lines on 8 DLang source 
files.
- One of them has a compilation error and quits.
- At this point I wait the completion of the other threads, but 
it would be faster to kill all those threads, fix the error, and 
run the multithreaded compilation again.

Is it safe to kill those processes, or would it be unreliable 
(because of the integrity of environment variables, and/or cached 
temp files)?

Thank You!

Imperatorn <johan_forsberg_86 hotmail.com> writes:

On Wednesday, 1 March 2023 at 11:38:11 UTC, realhet wrote:
 Hello,

 Is it safe to kill an ongoing LDC2 process on Windows?

 My situation is this:
 - I launch 8 LDC2 compilation command lines on 8 DLang source 
 files.
 - One of them has a compilation error and quits.
 - At this point I wait the completion of the other threads, but 
 it would be faster to kill all those threads, fix the error, 
 and run the multithreaded compilation again.

 Is it safe to kill those processes, or would it be unreliable 
 (because of the integrity of environment variables, and/or 
 cached temp files)?

 Thank You!

We don't know what you mean by your definition of safe 
unfortunately

realhet <real_het hotmail.com> writes:

On Friday, 3 March 2023 at 14:33:08 UTC, Imperatorn wrote:
 We don't know what you mean by your definition of safe 
 unfortunately

For example killing ldc2.exe while it writes some cached temp 
files.
And when the next time it tries to load those corrupted files, it 
will crash, or generate wrong output.