This dll is part of the windows kernel, and you usually don't have to worry
about it. There are some situations, however, where your program may seem to
hang exactly there.
Try the following: First, go to Tools->Options->Debugging->Native and Check
"Load DLL Exports", this gives some meaning to the addresses in *all* dlls
and is very usefull. Then, look at the call stack when you program seems to
hang. All calls to NTDLL go through the kernel32.dll, so you have a hint
what you where doing when your program hung.
Another tip: If the call stack says that your program hangs in a function
called WaitForCriticalSection or something similar, you have a
deadlock-problem.
"Tim Peer" <ti******@yahoo.com> schrieb im Newsbeitrag
news:04****************************@phx.gbl...
Are the debug symbols for 'c:\WINNT\system32\NTDLL.DLL'
available anywhere? I am debugging a multi-threaded
application and it appears to get hang in NTDLL.
Any help would be appreciated.
Thanks!