Fresh build of the tools and what version of windows?
@a.harker and I had some fun last night and found a way to reproduce; it only happens under certain compiler settings, which is fun. Pretty sure we’ve zapped it, IAC.
Nothing to do with windows versions - it was a very hard to spot sequencing bug where I’d written something like:
writethingAToFile() & writeThingBToFile();
(both functions return a bool) - the bitwise and does not ensure ordering, so the compiler can call the functions in either order (which is obviously bad if you expect them to be in order in the file). Had it been a logical and (&&) or the calls had been on separate lines this would not be allowed. Thus difference compiler settings may or may not produce the bug. I was using bitwise and because I was doing a lot of &= (there is not logical and equivalent) and so it seemed to make sense.
Thankfully Owen patiently stepped through and found it.