Hi all,
I want to debug a Windows NT4 SP6 with the lastest version of WinDbg but I
get a “Unable to get program counter” message and cant continue.
I have tried with older version of WinDbg keeping the same config. and it
works fine but still have problems with symbols. Its like NT4 symbols were
not found on server, its possible?
How do you debug for NT4 ?
Thanks
J.
Waiting to reconnect…
Connected to Windows NT 4 1381 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: SRV*b:\out**
http://msdl.microsoft.com/download/symbols
Executable search path is: B:\out
Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntoskrnl.exe -
ModLoad: 80100000 801db000 ntoskrnl.exe
CS descriptor lookup failed
Windows NT 4 Kernel Version 1381 UP Free x86 compatible
Kernel base = 0x80100000 PsLoadedModuleList = 0x80150b70
System Uptime: not available
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Force unload of ntoskrnl.exe
ModLoad: 80100000 801db000 ntoskrnl.exe
Unable to get program counter
WaitForEvent failed
Unable to get program counter
0008:497a 50 push ax
kd> G
^ Unable to get program counter ‘G’
I don’t know the answer to this, but it really wouldn’t surprise me, as
it hasn’t been a supported target for driver development in a long time.
I’m not really sure how long, but I can tell you that in the three
years or so that I’ve participated on these lists, I can recall NT4
coming up only three times. Also, there are no symbol downloads on this
page, so I really kind of doubt it is supported:
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
If you still have or can get your hands on a copy of the NT DDK of the
right service pack, you might be able to use the images and symbols in
the “debug” folder, but that is just a total guess.
Good luck,
mm
Julián de Navascués wrote:
Hi all,
I want to debug a Windows NT4 SP6 with the lastest version of WinDbg but
I get a “Unable to get program counter” message and cant continue.
I have tried with older version of WinDbg keeping the same config. and
it works fine but still have problems with symbols. Its like NT4 symbols
were not found on server, its possible?
How do you debug for NT4 ?
Thanks
J.
Waiting to reconnect…
Connected to Windows NT 4 1381 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*b:\out**http://msdl.microsoft.com/download/symbols
Executable search path is: B:\out
Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
ModLoad: 80100000 801db000 ntoskrnl.exe
CS descriptor lookup failed
Windows NT 4 Kernel Version 1381 UP Free x86 compatible
Kernel base = 0x80100000 PsLoadedModuleList = 0x80150b70
System Uptime: not available
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Force unload of ntoskrnl.exe
ModLoad: 80100000 801db000 ntoskrnl.exe
Unable to get program counter
WaitForEvent failed
Unable to get program counter
0008:497a 50 push ax
kd> G
^ Unable to get program counter ‘G’
By the way, your symbol problem is at least partially due to having an
extra ‘*’ in your sympath:
> SRV*b:\out**http://msdl.microsoft.com/download/symbols
I don’t imagine that it has any issues with using the ‘b:’ drive, but if
all else fails, I suppose I would try changing that.
Martin O’Brien wrote:
I don’t know the answer to this, but it really wouldn’t surprise me, as
it hasn’t been a supported target for driver development in a long time.
I’m not really sure how long, but I can tell you that in the three
years or so that I’ve participated on these lists, I can recall NT4
coming up only three times. Also, there are no symbol downloads on this
page, so I really kind of doubt it is supported:
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
If you still have or can get your hands on a copy of the NT DDK of the
right service pack, you might be able to use the images and symbols in
the “debug” folder, but that is just a total guess.
Good luck,
mm
Julián de Navascués wrote:
> Hi all,
>
> I want to debug a Windows NT4 SP6 with the lastest version of WinDbg
> but I get a “Unable to get program counter” message and cant continue.
>
> I have tried with older version of WinDbg keeping the same config. and
> it works fine but still have problems with symbols. Its like NT4
> symbols were not found on server, its possible?
>
> How do you debug for NT4 ?
>
> Thanks
>
> J.
>
> Waiting to reconnect…
> Connected to Windows NT 4 1381 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
> SRV*b:\out**http://msdl.microsoft.com/download/symbols
> Executable search path is: B:\out
> Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for ntoskrnl.exe -
> ModLoad: 80100000 801db000 ntoskrnl.exe
> CS descriptor lookup failed
> Windows NT 4 Kernel Version 1381 UP Free x86 compatible
> Kernel base = 0x80100000 PsLoadedModuleList = 0x80150b70
> System Uptime: not available
> Loaded dbghelp extension DLL
> Loaded ext extension DLL
> Loaded kext extension DLL
> Loaded kdextx86 extension DLL
> Force unload of ntoskrnl.exe
> ModLoad: 80100000 801db000 ntoskrnl.exe
> Unable to get program counter
> WaitForEvent failed
> Unable to get program counter
> 0008:497a 50 push ax
> kd> G
> ^ Unable to get program counter ‘G’
> I want to debug a Windows NT4 SP6 with the lastest version of WinDbg but
I get a “Unable to get program counter” message and cant continue.
I have not needed to debug on NT4 for a while. It would not be
surprising if MS finally dropped compatibility with NT4 in recent
debugger releases.
I have tried with older version of WinDbg keeping the same config. and
it works fine but still have problems with symbols. Its like NT4 symbols
were not found on server, its possible?
How do you debug for NT4 ?
I do not think NT4 symbols were ever on the symbol server. You will need
to get the symbol package(s), extract to your local drive, and add the
relevent folders to your debugger symbol path.
It looks like the symbol packages are no longer publicly available for
download from MS.
Joe Lowe
Pismo Technic Inc.
Yes, I guess it was discontinued too much time ago to expect that symbols
are on server.
Thanks for the second advice too.
B: is just a symbolic link to a directory with source and my own symbols.
regards
Julian
On Wed, Mar 12, 2008 at 6:08 PM, Martin O’Brien
wrote:
> By the way, your symbol problem is at least partially due to having an
> extra '’ in your sympath:
>
> >> SRVb:\out http://msdl.microsoft.com/download/symbols
>
> I don’t imagine that it has any issues with using the ‘b:’ drive, but if
> all else fails, I suppose I would try changing that.
>
>
> Martin O’Brien wrote:
> > I don’t know the answer to this, but it really wouldn’t surprise me, as
> > it hasn’t been a supported target for driver development in a long time.
> > I’m not really sure how long, but I can tell you that in the three
> > years or so that I’ve participated on these lists, I can recall NT4
> > coming up only three times. Also, there are no symbol downloads on this
> > page, so I really kind of doubt it is supported:
> >
> > http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
> >
> > If you still have or can get your hands on a copy of the NT DDK of the
> > right service pack, you might be able to use the images and symbols in
> > the “debug” folder, but that is just a total guess.
> >
> >
> > Good luck,
> >
> > mm
> >
> > Juli?n de Navascu?s wrote:
> >> Hi all,
> >>
> >> I want to debug a Windows NT4 SP6 with the lastest version of WinDbg
> >> but I get a “Unable to get program counter” message and cant continue.
> >>
> >> I have tried with older version of WinDbg keeping the same config. and
> >> it works fine but still have problems with symbols. Its like NT4
> >> symbols were not found on server, its possible?
> >>
> >> How do you debug for NT4 ?
> >>
> >> Thanks
> >>
> >> J.
> >>
> >> Waiting to reconnect…
> >> Connected to Windows NT 4 1381 x86 compatible target, ptr64 FALSE
> >> Kernel Debugger connection established.
> >> Symbol search path is:
> >> SRV*b:\out http://msdl.microsoft.com/download/symbols
> >> Executable search path is: B:\out
> >> Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
> >> *** ERROR: Symbol file could not be found. Defaulted to export
> >> symbols for ntoskrnl.exe -
> >> ModLoad: 80100000 801db000 ntoskrnl.exe
> >> CS descriptor lookup failed
> >> Windows NT 4 Kernel Version 1381 UP Free x86 compatible
> >> Kernel base = 0x80100000 PsLoadedModuleList = 0x80150b70
> >> System Uptime: not available
> >> Loaded dbghelp extension DLL
> >> Loaded ext extension DLL
> >> Loaded kext extension DLL
> >> Loaded kdextx86 extension DLL
> >> Force unload of ntoskrnl.exe
> >> ModLoad: 80100000 801db000 ntoskrnl.exe
> >> Unable to get program counter
> >> WaitForEvent failed
> >> Unable to get program counter
> >> 0008:497a 50 push ax
> >> kd> G
> >> ^ Unable to get program counter ‘G’
> >
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
It looks like the symbol packages are no longer publicly available for
download from MS. <- you are right 
I have been looking for them in
MSDN and anywhere and I have not found symbols for NT4.
I have read about extracting symbols from a Windows NT CD… thats the next
step. Thanks
On Wed, Mar 12, 2008 at 6:26 PM, Joe Lowe wrote:
> > I want to debug a Windows NT4 SP6 with the lastest version of WinDbg but
> > I get a “Unable to get program counter” message and cant continue.
>
> I have not needed to debug on NT4 for a while. It would not be
> surprising if MS finally dropped compatibility with NT4 in recent
> debugger releases.
>
> > I have tried with older version of WinDbg keeping the same config. and
> > it works fine but still have problems with symbols. Its like NT4 symbols
> > were not found on server, its possible?
> >
> > How do you debug for NT4 ?
>
> I do not think NT4 symbols were ever on the symbol server. You will need
> to get the symbol package(s), extract to your local drive, and add the
> relevent folders to your debugger symbol path.
>
> It looks like the symbol packages are no longer publicly available for
> download from MS.
>
> Joe Lowe
> Pismo Technic Inc.
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>