things of note, too:
- Only crashes if I have a saved run in progress
- DOESN'T crash if I run as admin directly from file explorer vs steam.
Verified files and am on most up to date windows, etc.
things of note, too:
- Only crashes if I have a saved run in progress
- DOESN'T crash if I run as admin directly from file explorer vs steam.
Verified files and am on most up to date windows, etc.
lldb: thread backtrace all
okay, fine
windbg: ~*kb
wat?
lldb: thread backtrace all
okay, fine
windbg: ~*kb
wat?
devblogs.microsoft.com ->
Unfortunately Microsoft doesn't seem to follow this wisdom:
github.com ->
#WinDbg
Original->
devblogs.microsoft.com ->
Unfortunately Microsoft doesn't seem to follow this wisdom:
github.com ->
#WinDbg
Original->
Although I have occasionally dived into WinDBG to have a look at assembly code. It's... Not fun.
Although I have occasionally dived into WinDBG to have a look at assembly code. It's... Not fun.
I've been having lots of Blue Screens so when a Firefox tab crashed, I opened the mindump in WinDbg to see what it was. The faulting instruction was "int 3". (Debugger Trap) Not one I have to worry about. 🤣
(Although it was in in WaitForMultipleObjects. 😖)
I've been having lots of Blue Screens so when a Firefox tab crashed, I opened the mindump in WinDbg to see what it was. The faulting instruction was "int 3". (Debugger Trap) Not one I have to worry about. 🤣
(Although it was in in WaitForMultipleObjects. 😖)