R-Goc

I don't know if there is any way to check all these. Also not completely sure about the branches in the cmake, but should be fine. Edit: clearly it's wrong...

What do you think about adding a cmake option to use the std stack trace instead of libbacktrace?

> This seems reasonable to me. Replacing this bespoke "print backtrace" impl that doesn't print quite enough information with a std version that might go the extra mile seems reasonable...

I was actually wondering about that. I though it was some WSL weirdness, but appears not. Looking at this we might want to change this backtrace to not include the...

It's ready on my side.

This stack trace doesn't even leave windows DLLs. Unless it is corrupted main wasn't even called. You might want to report it to one of the Microsoft forums, not sure...

Seems a bit weird then that it would cause this error.

Nevermind you're right. Rtlp­Handle­Invalid­User­Call­Target handles a call to an invalid function pointer.

If you could read the registers it would be nice. The function pointer should still be there.

That is my suspicion. As long as this can be reproduced and you check where the pointer points to it should be done.