WSL: How to debug complete subsystem hang?
I’ve experienced this a number of times, but pretty sporadically, and I’m not sure how to go about getting information that would help debug this.
Sometimes after performing an action in the WSL environment, I end up with a completely deadlocked lxss where all existing (launched) WSL processes immediately become unresponsive and any new commands (even just bash) hang indefinitely.
I just experienced this on 16299.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 15 (6 by maintainers)
A typical setup is a dev box and a test machine or test VM with a kernel debugger attached. Personally I use one physical machine and a couple VMs with different memory and virtual processor counts.
They’re actually old features, but the article was recently updated. So long as your PC isn’t crashed (BSoD/GSoD) or totally hung, local kdb is fine.