flat assembler
Message board for the users of flat assembler.
Index
> IDE Development > if cancel compile, write failed on next compile |
Author |
|
baldr 03 Apr 2014, 13:28
edfed,
Since Cancel means TerminateThread(), it could be so (though the window of opportunity is not so wide, you have to be [un]lucky enough). |
|||
03 Apr 2014, 13:28 |
|
AsmGuru62 03 Apr 2014, 14:04
TerminateThread should never be used anywhere.
|
|||
03 Apr 2014, 14:04 |
|
Tomasz Grysztar 03 Apr 2014, 20:43
baldr wrote: Since Cancel means TerminateThread(), it could be so (though the window of opportunity is not so wide, you have to be [un]lucky enough). AsmGuru62 wrote: TerminateThread should never be used anywhere. Actually, in the case of fasm's thread, its only weak spots are the file access and allocation of main memory block. If some kind of mutex was introduced to prevent thread termination in these few vulnerable places, all the rest of fasm's code is safe to be terminated at any moment, simply because it uses no external functions and operates within its own data structures that are re-created from scratch inside that single memory block each time the thread is started, overwriting any possible leftover from the previous thread executions. I did not put any safeties into those few weak spots simply because I belittled the chances of actually hitting the mark and landing in one of them when pressing "Cancel". |
|||
03 Apr 2014, 20:43 |
|
fasmnewbie 04 Apr 2014, 20:11
I don't know if this is related, but I once had a consistent problem with "Error: Write Failed" when I was on Win 8 and using multiple version of FASMW and even FASM. I had to wait for almost a minute to enable me to run my code after the "write failed" compilation. The workaround;
1. Compatibility: Lowered to WinXP SP 2 2. Enabled write/disk cache on the disk. Can't remember the exact steps but it was something on the Disk property's Policy. Problems gone. I think this has nothing to do with FASM. |
|||
04 Apr 2014, 20:11 |
|
edfed 05 Apr 2014, 12:29
i think this have something to do with the win32api used in fasmw.
i am currentlly a beginner in win32, cause i use msdn a lot in my job, and what i see is a blurry compatibility frontier between original and new win api designs... mybe fasm for vista 7 and 8 should have a different code to do file operations. |
|||
05 Apr 2014, 12:29 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.