Can anyone help explain this call stack? We have written a managed code DDL
that runs as an add-in for a third-party (unmanaged) server product. Things
usually work well, but occasionally we get some hung threads that all show
this call stack. None of out code is on the stack, but mscorwks is. What
is going on here?
[ 1] 0x7ffe0304 +2147353271 (77e41bfa,3,4184fec4,1)
[ 2] 0x77f4372d ntdll.NtWaitForMultipleObjects+12 (3,4184ff5c,0,ffffffff)
[ 3] 0x77e4b0e4 KERNEL32.WaitForMultipleObjects+23 (0,0,0,791d24ee)
[ 4] 0x791d167e mscorwks+136830 (41741eb0,0,0,41741eb0)
[ 5] 0x77e4a990 KERNEL32.FlsSetValue+1913 (791d24e3,41741eb0,0,41cb263c)
"Jeffrey Tan[MSFT]" - 16 Feb 2006 06:21 GMT
Hi Stephen,
Thanks for your post.
Do you setup the symbols correctly for the debugger? From the call stack,
it seems that some symbols are not shown out.
Also, I do not think the pure call stack without user written code is
helpful to troubleshooting out the root cause regarding your problem. You'd
better explain your main work in corresponding technology groups to check
if you are doing the correct thing. Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Jim Cheshire - 01 Apr 2006 04:23 GMT
>Can anyone help explain this call stack? We have written a managed code DDL
>that runs as an add-in for a third-party (unmanaged) server product. Things
[quoted text clipped - 7 lines]
>[ 4] 0x791d167e mscorwks+136830 (41741eb0,0,0,41741eb0)
>[ 5] 0x77e4a990 KERNEL32.FlsSetValue+1913 (791d24e3,41741eb0,0,41cb263c)
Your symbols aren't lining up, so this stack useful. It also looks
like you might have some managed executing in here which is not going
to show up when using kp.
Jim