A stack trace (or even better, a minidump with the call stack!) is one of the most useful debugging things for me. Hell, the call stack in general is super useful to me!
I can look at a stack trace, go "oh, function X is misbehaving after being called by function Y, from function Z", and work out what's gone wrong from the context clues, and other debugger info. As a game developer, with codebases that are big, semi-monolithic codebases, it's essential, especially when code crosses the gameplay/engine and engine/kernel barriers.
It's funny, as my phone (A 2022 Moto Razr) can work as PC, if I plug it into a monitor with it's USB-C port. I can plug it into a monitor, and plug a mouse and keyboard into the monitor's inbuilt USB-C hub, and it works just fine. Has a desktop mode and everything! If the monitor doesn't have a hub in it, I can use the phone as a mouse/touchpad! Plus, if the monitor supports it, it'll even keep it charged rather than using the battery!
And I don't just use it as a gimmick, I use a HDMI/USB-C cable to use it with my TV as a streaming/light gaming setup. Nice to be able to plug it in, kick off a streaming app or Youtube, or play some Minecraft or something on my TV in bed, all comfy.
I can look at a stack trace, go "oh, function X is misbehaving after being called by function Y, from function Z", and work out what's gone wrong from the context clues, and other debugger info. As a game developer, with codebases that are big, semi-monolithic codebases, it's essential, especially when code crosses the gameplay/engine and engine/kernel barriers.