Not working as expected .. about delete-self-poc

[evandrix]

i managed to reproduce the error, by simply compiling it manually, using cl.exe directly e.g. cl.exe main.c.
it prints [LOG] - attempting to rename file name, as described, and empties the file.

so i decided to make a new C++ Console Application on MSVC 2019, the compilation exe output worked perfectly then.
looking at the full command line for compilation cl.exe main.c /permissive- /GS /GL /W3 /Gy /Zc:wchar_t /Zi /Gm- /O2 /sdl /Zc:inline /fp:precise /D "NDEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /errorReport:prompt /WX- /Zc:forScope /Gd /Oi /MT /FC /EHsc /nologo /diagnostics:column, and removing parameters in various combinations, it seems like cl.exe main.c /Oi is the bare minimal that works.

official documentation https://docs.microsoft.com/en-us/cpp/build/reference/oi-generate-intrinsic-functions?view=msvc-160

also, fixed 3 warnings by specifying the (W)ide variant of the Win32 API functions e.g. CreateFileW, GetModuleFileNameW and PathFileExistsW.

[0x413x4]

Worked fine on the following:

• Windows 10 1909 - OS Build: 18363
• Windows 10 20H2 - OS Build: 19042

Compiled manually using cl.exe main.c and then running main.exe as admin.

[FunnyWolf]

Worked fine :

• Windows 10 1909
• VS2019

[LloydLabs]

Is there any chance that the binaries could be shared, so I can identify the exact problem with the compiler. It's quite interesting, that under some optimisations it'll hang - others it'll not. This may also be a bug with MSVC, which could be even all the more interesting!

I've changed the function prefix to explicitly the wide-character variations - apologies, this was down to my project settings for VS2019 where UNICODE was defined in the project settings.

[CaledoniaProject]

@LloydLabs Attached binary. Just rename main.txt to main.exe.

It's compiled with VS2019 16.8.4 command line tools, aka cl main.c, with latest master branch.

I think you should reopen it:

1. I don't think optimization has anything to do with the hanging issue.
2. What about the file size issue? Do right click on the main.exe after execution, and the size on disk is still 124KB.

[LloydLabs]

I'm unsure, @CaledoniaProject, your issue seems isolated - and not able to be reproduced on other environments. I will re-open the issue, though. The fact you can right-click on the context menu, and choose properties, is an issue by itself. You shouldn't be able to do that to the file.

The root cause of your issue is that the file is not deleted in the first place. Which, as abovementioned, I'm sure is an isolated issue. Do you have any anti-virus or endpoint-detection system on your machine that may be interfering with this?