My program, which has a JIT compiler in it, is getting killed (or at least it seems like) on azure pipelines. when i turn the JIT off it runs fine. when i use IMAGE_NAME: 'windows-2019' instead of -latest, it runs fine.
Is there some kind of new security feature or exploit mitigation or whatever that was turned on some time between these two images that might be killing my program because the jit needs to be adapted to it?
How the heck do i find out how my program is actually quitting? "exit code 0xff" is not terribly enlightening ...
This is incredibly frustrating to debug, not just because I have to wait ~10 minutes between putting a change in and seeing the result, and the majority of tools windows developers have at their disposal seem to only be usable with a GUI which, surprise surprise, azure pipelines runners don't let you access.

#azurepipelines #msvc #windows #justintimecompilation #ETW #pwsh

Can anyone suggest a good textbook for a VM's and JIT compilation course? You might think that would be too specialized for textbooks, but you'd be wrong. I like Smith and Nair book a lot, but it's almost 20 years old now, and uh, one or two things have happened. #VirtualMachines #JustInTimeCompilation #TextBook