Re: Frame-based exception handling problem on Server 2008
- From: roger.orr@xxxxxxxxx
- Date: Fri, 22 Feb 2008 04:56:57 -0800 (PST)
On Feb 21, 4:54 pm, Corinna Vinschen <cori...@xxxxxxxxxxxxxxxx> wrote:
Hi,
while testing Cygwin on Server 2008, I encountered a couple of spurious
hangs in OS functions, taking as much CPU it can get. This happens only
on Server 2008, both, 32 and 64 bit version, but it does not happen on
any other Windows version, up to and including Vista SP1.
Debugging turned up that Server 2008 has apparently a problem with
Cygwin's exception handling.
Curious.
What is the call stack, including kernel entries?
One easy way to get this is using Process Explorer:
Find process,
right click and select Properties..
go to Threads tab
Find thread in loop
Click Stack
That info might help understand the problem.
Out of interest, why does the exception handler chain end in a loop?
I'd always assumed that if an exception handler didn't return the
"continue search" value then there would be no reason to even read
the pointer to prev value.
Regards,
Roger.
.
- Follow-Ups:
- Re: Frame-based exception handling problem on Server 2008
- From: Corinna Vinschen
- Re: Frame-based exception handling problem on Server 2008
- References:
- Frame-based exception handling problem on Server 2008
- From: Corinna Vinschen
- Frame-based exception handling problem on Server 2008
- Prev by Date: Re: Is a file system driver my only option?
- Next by Date: Mutex and spinlocks
- Previous by thread: Re: Frame-based exception handling problem on Server 2008
- Next by thread: Re: Frame-based exception handling problem on Server 2008
- Index(es):
Relevant Pages
|