Error: Unknown exception [at bdump (line 128 col 5)] about bdump HOT 3 CLOSED

Resolved.
I saw 0vercl0k/wtf@e278c94 today 😂
after running !wow64exts.sw command, currentProcess and currentThread appears correctly.

from bdump.

Thanks for the full logs and exhaustive testing!

Unless I've misunderstood something, host.currentThread should essentially always exist, meaning this would be a windbg bug. I'm not really sure how I could handle this other than dumping the regs with r and parsing them out, but that seems pretty gross. If you set the breakpoint a few instructions early then step to your location, does that help convince windbg to create host.currentThread. Does host.currentThread exist in other windbg contexts? (e.g. notepad.exe, etc).

from bdump.

I tried (1) set the breakpoint a few instructions early (2) dump cmd.exe, but it raises same error

Thank you for answering, and I'll try to find another way.

from bdump.