Re: Unhandled exception when pushing esi
- From: "Oracle" <wong.kam.keung@xxxxxxxxx>
- Date: 27 May 2006 13:54:50 -0700
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]
- Unhandled exception when pushing esi
- Prev by Date: Re: Punting DrvTextOut and DrvStrokePath causes BSOD in mirror driver, why?
- Next by Date: Re: KMDF USB: Safely handling multiple child requests
- Previous by thread: Re: Unhandled exception when pushing esi
- Next by thread: Re: Unhandled exception when pushing esi
- Index(es):
Relevant Pages
|