That is needed for Rec Room which does RtlCaptureStackBackTrace() from inside obfuscated code without runtime info. That is not about RtlCaptureStackBackTrace() crashing (it wasn't actually here). The game does own checks on return addresses and fails those on bogus addresses returned from unwinding through the functions without unwind info (treated as leaf functions). I think there is some logic in this stack walk behaviour as only leaf functions can be missing unwind info and leaf functions are not supposed to call anything and thus appear in stack traces. However, this behaviour breaks RtlCaptureStackBackTrace() when, e. g., there is an access violation in leaf function and RtlCaptureStackBackTrace() is called from exception handler (I tested that separately by forcing access violation in a function without runtime function and capturing stack trace from VEH handler). The weird thing is that, as far as tests go, Windows doesn't seem to take dynamic runtime functions into account and only minds the unwind info from PE module (and stops back trace even if there is dynamic unwind info available for it). I didn't implement that part (still considering any runtime function to be enough to continue back trace), reasoning that this weird behaviour will only complicate things without clear benefit (until something depends specifically on that part). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9944#note_127662