Windows: segfault in `RtlGetLengthWithoutLastFullDosOrNtPathElement` seemingly innocuous, but gets trapped anyways

[hazelduvall]

Key	Value
Edition	Windows 11 Pro
Version	22H2
OS build	22621.1992
Experience	Windows Feature Experience Pack 1000.22644.1000.0
Processor	12th Gen Intel(R) Core(TM) i7-12800H 2.40 GHz
Installed RAM	64.0 GB (63.7 GB usable)
System type	64-bit operating system, x64-based processor

I've recently updated Windows and suddenly there are a ton of segfaults inside this ntdll function. I believe segfaults are innocuous because:

• They do not occur or are handled seamlessly when running inside a debugger (Visual Studio, WinDbg)
• Not enabling this library allows the application to run smoothly
• A compliant call to a function like OutputDebugStringA triggers it

However, with this library loaded into the process, the application cannot run because of all the segfaults it detects.

I am not confident this library is still maintained, so I have not provided a minimal reproducible example for the sake of debugging, and am mostly just posting this issue so that search engines pick it up. However, if someone is interested in fixing this, I would be happy to provide such an example.

[alberto-i]

Did you resolve this issue anyway?

[hazelduvall]

I resolved this issue by not using this library :)

Unsure if it still replicates, I think the above information might be enough to create an example though? It's been a while since I took a look at this.

[tstiemerling]

Same issue here