I am a big fan of puzzle solving. I said to people in my office that if they have a difficult bug that I'd try solving it.
I've seen a lot of bad code and I'm skilled at debugging realtime multithreaded apps. So, when you have a corporate app that runs many events in a short period of time, you have X different call stacks with ~10 functions and nobody can remember all that so I write down the call stacks I find potentially problematic. After that, I go through all the call stacks, sometimes it's the interaction between them causing the bug.
I am a big fan of puzzle solving. I said to people in my office that if they have a difficult bug that I'd try solving it.
I've seen a lot of bad code and I'm skilled at debugging realtime multithreaded apps. So, when you have a corporate app that runs many events in a short period of time, you have X different call stacks with ~10 functions and nobody can remember all that so I write down the call stacks I find potentially problematic. After that, I go through all the call stacks, sometimes it's the interaction between them causing the bug.
Interesting, thanks for sharing your approach