Hi Dan,
thanks for your message. Unfortunately when it comes to WinDBG I’m a real
rookie. I’ve had a look at the documentation, but it didn’t tell me much.
What I’m trying to say: I don’t know how to look at any IRPs or find out
what the current thread was doing. And I always thought an ISR would get a
“fresh” kernelmode stack…
However, this is not my highest priority right now, so I’ll just let it
rest for a while.
Cheers, Paul
xxxxx@lists.osr.com schrieb am 16.10.2007 16:58:31:
Try to find out what the current thread is doing that is using so much
stack. The debugger seems to be showing only the context of your
interrupt,
but you can use dds to find likely call frames, and k = … to display
the
stack.
I’d also look at the IRP listed in the !thread output. That might tell
you
something.
It’s interesting that windbg thinks the current stack pointer is
baa6677c,
which would leave plenty of space.
- Dan.
-----Original Message-----
…