Re: Unhandled exception when pushing esi
- From: "David J. Craig" <Dave@xxxxxxxxxxxxx>
- Date: Sat, 27 May 2006 19:16:15 -0700
12KB is not the 'usual', it is the fixed unchanging size. 16KB on x64. The
kernel guys said that it would not be increased according to Microsoft at
one of the IFS PlugFests.
"Skywing" <skywing_NO_SPAM_@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uW7IaPfgGHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
`!thread' will tell you about the stack region for a particular thread
(assuming you have enough information saved in your dump file).
By default, non-GUI threads will have around 12K of kernel stack on x86
systems, I believe. If you need to check this at runtime, there is an
`IoGetRemainingStackSize' call that you can use in kernel mode.
"Oracle" <wong.kam.keung@xxxxxxxxx> wrote in message
news:1148763290.206786.302740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ivan,
Is there a way that I can check the currently used stack size for that
thread in the dump file? What will be the usual size limit for a kernel
stack for a thread?
Thanks for any advice.
Ivan Brugiolo [MSFT] wrote:
My wild guess would be that you have exhausted the kernel stack
for that thread, by either creating a large on-the-stack variable,
of, by calling some _alloca() derivative function.
.
- Follow-Ups:
- Re: Unhandled exception when pushing esi
- From: Skywing
- Re: Unhandled exception when pushing esi
- References:
- Unhandled exception when pushing esi
- From: wong . kam . keung
- Re: Unhandled exception when pushing esi
- From: Ivan Brugiolo [MSFT]
- Re: Unhandled exception when pushing esi
- From: Oracle
- Re: Unhandled exception when pushing esi
- From: Skywing
- Unhandled exception when pushing esi
- Prev by Date: Re: Unhandled exception when pushing esi
- Next by Date: Re: Punting DrvTextOut and DrvStrokePath causes BSOD in mirror driver, why?
- Previous by thread: Re: Unhandled exception when pushing esi
- Next by thread: Re: Unhandled exception when pushing esi
- Index(es):
Relevant Pages
|
|