I am getting the following error on firing the !lock windbg command
NTSDEXTS: Unable to resolve ntdll!RtlCriticalSectionList
NTSDEXTS: Please check your symbols
I am using:
Windbg version: Version 6.0
Windows OS: Vista
Any resolution for the issue?
Download the most recent version of windbg (part of the WDK) and hope for
the best.
Good luck,
Mm
On Dec 31, 2010 12:58 PM, wrote:
> I am getting the following error on firing the !lock windbg command
> NTSDEXTS: Unable to resolve ntdll!RtlCriticalSectionList
> NTSDEXTS: Please check your symbols
>
> I am using:
> Windbg version: Version 6.0
> Windows OS: Vista
>
> Any resolution for the issue?
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Your symbols are not configure correctly.
Add this path to your symbols path and hit .reload :
*SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols\*
Thanks,
Elad
On Fri, Dec 31, 2010 at 8:27 PM, Martin O’Brien <
xxxxx@gmail.com> wrote:
Download the most recent version of windbg (part of the WDK) and hope for
the best.Good luck,
Mm
On Dec 31, 2010 12:58 PM, wrote:
> > I am getting the following error on firing the !lock windbg command
> > NTSDEXTS: Unable to resolve ntdll!RtlCriticalSectionList
> > NTSDEXTS: Please check your symbols
> >
> > I am using:
> > Windbg version: Version 6.0
> > Windows OS: Vista
> >
> > Any resolution for the issue?
> >
> >
> > —
> > WINDBG is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Thanks MM and Elad for the reply.
MM I will first try with symbols solution before installing the new Windbg.
Elad I changed the symbol download path as suggested but it did not resolved the issue.
When will the symbols and dlls get downloaded to the local folder?
The symbols will gets downloaded to the local folder whenever a module is
loaded or accessed. !locks should trigger windbg to download the symbols.
Do the following steps :
Open windbg, add the symbol server path I gave you. run !sym noisy and then
.reload.
after that do the !locks and post the output you have from the !sym noisy to
this thread.
Thanks,
Elad
On Fri, Dec 31, 2010 at 9:27 PM, wrote:
> Thanks MM and Elad for the reply.
> MM I will first try with symbols solution before installing the new Windbg.
> Elad I changed the symbol download path as suggested but it did not
> resolved the issue.
> When will the symbols and dlls get downloaded to the local folder?
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Unless your symbols are completely screwed up, given that it’s ntdll at
issue, I don’t think that symbols are your problem, per se, but certainly
give it a try.
Mm
On Dec 31, 2010 2:25 PM, wrote:
> Thanks MM and Elad for the reply.
> MM I will first try with symbols solution before installing the new
Windbg.
> Elad I changed the symbol download path as suggested but it did not
resolved the issue.
> When will the symbols and dlls get downloaded to the local folder?
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I downloaded teh latest symbols Windows_Longhorn.6001.080118-1840.x86fre.Symbols.exe and the !lock command is now working fine.
Thanks MM and Elad for the inputs.
Cool
On Dec 31, 2010 3:41 PM, wrote:
> I downloaded teh latest symbols
Windows_Longhorn.6001.080118-1840.x86fre.Symbols.exe and the !lock command
is now working fine.
> Thanks MM and Elad for the inputs.
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
It means that you dont have access to microsoft symbol server for some
reason (proxy, restricted zone ? ) or you didn’t set the symbols right.
There is no real reason to use a local copy of the symbols if you do have an
internet access (and when you have access to microsoft symbols).
Anyway, glad it worked out 
Thanks,
Elad
On Fri, Dec 31, 2010 at 10:54 PM, Martin O’Brien <
xxxxx@gmail.com> wrote:
Cool
On Dec 31, 2010 3:41 PM, wrote:
> > I downloaded teh latest symbols
> Windows_Longhorn.6001.080118-1840.x86fre.Symbols.exe and the !lock command
> is now working fine.
> > Thanks MM and Elad for the inputs.
> >
> >
> > —
> > WINDBG is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer