Your debugger is not using the correct symbols

WINDBG
1

I was debugging happily for long time with pointing MS web symbol
server.

But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
debug and it always complains about “not using correct symbols”

This is the output I get for “lm lv”:

0: kd> lm lv

start end module name

80800000 80a56000 nt (pdb symbols)
.\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

Loaded symbol image file: ntkrpamp.exe

Image path: ntkrpamp.exe

Image name: ntkrpamp.exe

Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

CheckSum: 0023D8B4

ImageSize: 00256000

File version: 5.2.3790.2825

Product version: 5.2.3790.2825

File flags: 0 (Mask 3F)

File OS: 40004 NT Win32

File type: 1.0 App

File date: 00000000.00000000

Translations: 0409.04b0

CompanyName: Microsoft Corporation

ProductName: Microsoft(r) Windows(r) Operating System

InternalName: ntkrpamp.exe

OriginalFilename: ntkrpamp.exe

ProductVersion: 5.2.3790.2825

FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

FileDescription: NT Kernel & System

LegalCopyright: (c) Microsoft Corporation. All rights reserved.

Could you guys shed some light?

Thanks

Ramaraj

2

I tried clearing/reloading/overwriting, etc. But I get same error. Could
somebody help me out of this? Thanks.

This is what I get when I do !process

0: kd> !process 0 7

**** NT ACTIVE PROCESS DUMP ****

************************************************************************
*

***
***

***
***

*** Your debugger is not using the correct symbols
***

***
***

*** In order for this command to work properly, your symbol path
***

*** must point to .pdb files that have full type information.
***

***
***

*** Certain .pdb files (such as the public OS symbols) do not
***

*** contain the required information. Contact the group that
***

*** provided you with these symbols if you need this command to
***

*** work.
***

***
***

*** Type referenced: nt!_LIST_ENTRY
***

***
***

************************************************************************
*

Unable to read _LIST_ENTRY @ 808ad0c8

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
Sent: Monday, July 02, 2007 3:36 PM
To: Kernel Debugging Interest List
Subject: [windbg] Your debugger is not using the correct symbols

I was debugging happily for long time with pointing MS web symbol
server.

But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
debug and it always complains about “not using correct symbols”

This is the output I get for “lm lv”:

0: kd> lm lv

start end module name

80800000 80a56000 nt (pdb symbols)
.\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

Loaded symbol image file: ntkrpamp.exe

Image path: ntkrpamp.exe

Image name: ntkrpamp.exe

Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

CheckSum: 0023D8B4

ImageSize: 00256000

File version: 5.2.3790.2825

Product version: 5.2.3790.2825

File flags: 0 (Mask 3F)

File OS: 40004 NT Win32

File type: 1.0 App

File date: 00000000.00000000

Translations: 0409.04b0

CompanyName: Microsoft Corporation

ProductName: Microsoft(r) Windows(r) Operating System

InternalName: ntkrpamp.exe

OriginalFilename: ntkrpamp.exe

ProductVersion: 5.2.3790.2825

FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

FileDescription: NT Kernel & System

LegalCopyright: (c) Microsoft Corporation. All rights reserved.

Could you guys shed some light?

Thanks

Ramaraj

You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Is the only error? If so, it looks like one of those cases where a type
(_LIST_ENTRY) got stripped and shouldn’t have before Microsoft shipped
the symbol file. That being said, I can’t say that I know what
‘websymbols,’ which makes me curious. Are you getting these from
http://msdl.microsoft.com/download/symbols and !sym noisy followed by
lml looks ok? Assuming that you are in fact already loading the best
matching symbols, I can tell you (roughly) how to resolve this specific
error.

  1. Create a header file with the definition of _LIST_ENTRY in it.

  2. Compile it with (among other switches) -Fp -TC, replacing
    with the fullpath of the file WinDbg is loading for ntoskrnl symbols.
    The -TC just compiles an H file as C.

    This will add the type _LIST_ENTRY which !process apparently needs.

    The other thing that I would recommend doing is checking this link
    (http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx) to see
    if the symbol package can be downloaded. I’ve had a couple of
    experiences where the symbol server had either incorrect or no symbols
    and this page did.

    I don’t know if this still happens, but a while back, in my opinion,
    Microsoft not commonly did not release symbols for some of the more
    esoteric os and service packs, particularly for checked builds. I don’t
    know if 2003 R2 falls in to the category, but I have never come across
    it.

    Good luck,

    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Tuesday, July 03, 2007 19:45
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] Your debugger is not using the correct symbols

    I tried clearing/reloading/overwriting, etc. But I get same error. Could
    somebody help me out of this? Thanks.

    This is what I get when I do !process

    0: kd> !process 0 7

    NT ACTIVE PROCESS DUMP










    Your debugger is not using the correct symbols


    In order for this command to work properly, your symbol path


     must point to .pdb files that have full type information.


    Certain .pdb files (such as the public OS symbols) do not


     contain the required information. Contact the group that


     provided you with these symbols if you need this command to


     work.


    Type referenced: nt!_LIST_ENTRY


    *
    *

    Unable to read _LIST_ENTRY @ 808ad0c8



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Monday, July 02, 2007 3:36 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Your debugger is not using the correct symbols

    I was debugging happily for long time with pointing MS web symbol
    server.

    But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
    debug and it always complains about “not using correct symbols”

    This is the output I get for “lm lv”:

    0: kd> lm lv

    start end module name

    80800000 80a56000 nt (pdb symbols)
    .\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

    Loaded symbol image file: ntkrpamp.exe

    Image path: ntkrpamp.exe

    Image name: ntkrpamp.exe

    Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

    CheckSum: 0023D8B4

    ImageSize: 00256000

    File version: 5.2.3790.2825

    Product version: 5.2.3790.2825

    File flags: 0 (Mask 3F)

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0409.04b0

    CompanyName: Microsoft Corporation

    ProductName: Microsoft(r) Windows(r) Operating System

    InternalName: ntkrpamp.exe

    OriginalFilename: ntkrpamp.exe

    ProductVersion: 5.2.3790.2825

    FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

    FileDescription: NT Kernel & System

    LegalCopyright: (c) Microsoft Corporation. All rights reserved.

    Could you guys shed some light?

    Thanks

    Ramaraj

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Small correction: the first switch in (2) should be -Fd, not -Fp.

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, July 03, 2007 20:04
To: Kernel Debugging Interest List
Subject: RE: [windbg] Your debugger is not using the correct symbols

Is the only error? If so, it looks like one of those cases where a type
(_LIST_ENTRY) got stripped and shouldn’t have before Microsoft shipped
the symbol file. That being said, I can’t say that I know what
‘websymbols,’ which makes me curious. Are you getting these from
http://msdl.microsoft.com/download/symbols and !sym noisy followed by
lml looks ok? Assuming that you are in fact already loading the best
matching symbols, I can tell you (roughly) how to resolve this specific
error.

  1. Create a header file with the definition of _LIST_ENTRY in it.

  2. Compile it with (among other switches) -Fp -TC, replacing
    with the fullpath of the file WinDbg is loading for ntoskrnl symbols.
    The -TC just compiles an H file as C.

    This will add the type _LIST_ENTRY which !process apparently needs.

    The other thing that I would recommend doing is checking this link
    (http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx) to see
    if the symbol package can be downloaded. I’ve had a couple of
    experiences where the symbol server had either incorrect or no symbols
    and this page did.

    I don’t know if this still happens, but a while back, in my opinion,
    Microsoft not commonly did not release symbols for some of the more
    esoteric os and service packs, particularly for checked builds. I don’t
    know if 2003 R2 falls in to the category, but I have never come across
    it.

    Good luck,

    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Tuesday, July 03, 2007 19:45
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] Your debugger is not using the correct symbols

    I tried clearing/reloading/overwriting, etc. But I get same error. Could
    somebody help me out of this? Thanks.

    This is what I get when I do !process

    0: kd> !process 0 7

    NT ACTIVE PROCESS DUMP










    Your debugger is not using the correct symbols


    In order for this command to work properly, your symbol path


     must point to .pdb files that have full type information.


    Certain .pdb files (such as the public OS symbols) do not


     contain the required information. Contact the group that


     provided you with these symbols if you need this command to


     work.


    Type referenced: nt!_LIST_ENTRY


    *
    *

    Unable to read _LIST_ENTRY @ 808ad0c8



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Monday, July 02, 2007 3:36 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Your debugger is not using the correct symbols

    I was debugging happily for long time with pointing MS web symbol
    server.

    But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
    debug and it always complains about “not using correct symbols”

    This is the output I get for “lm lv”:

    0: kd> lm lv

    start end module name

    80800000 80a56000 nt (pdb symbols)
    .\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

    Loaded symbol image file: ntkrpamp.exe

    Image path: ntkrpamp.exe

    Image name: ntkrpamp.exe

    Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

    CheckSum: 0023D8B4

    ImageSize: 00256000

    File version: 5.2.3790.2825

    Product version: 5.2.3790.2825

    File flags: 0 (Mask 3F)

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0409.04b0

    CompanyName: Microsoft Corporation

    ProductName: Microsoft(r) Windows(r) Operating System

    InternalName: ntkrpamp.exe

    OriginalFilename: ntkrpamp.exe

    ProductVersion: 5.2.3790.2825

    FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

    FileDescription: NT Kernel & System

    LegalCopyright: (c) Microsoft Corporation. All rights reserved.

    Could you guys shed some light?

    Thanks

    Ramaraj

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

5

some times the pdbs simply dont play nice

http://www.osronline.com/showThread.cfm?link=108519

like i stated i simply ditched the whole directory of symbols and
refetched all the symbols and the problems simply disasspeared
mysteriously

also look for some non expanded pdbs in the symbol path like
ntoskrnl.pd_

some botched attempt at previous symbol retrieval can cause symbol
problems as well

regards

raj

On 7/4/07, Ramaraj Pandian wrote:
>
>
>
> I tried clearing/reloading/overwriting, etc. But I get same error. Could
> somebody help me out of this? Thanks.
>
>
>
> This is what I get when I do !process
>
> 0: kd> !process 0 7
>
> NT ACTIVE PROCESS DUMP
>
>
>
>
>
>
>
>
>
> Your debugger is not using the correct symbols
>
>
>
>
> In order for this command to work properly, your symbol path
>
> must point to .pdb files that have full type information.
>
>
>
>
> Certain .pdb files (such as the public OS symbols) do not
>
> contain the required information. Contact the group that
>
> provided you with these symbols if you need this command to
>
> work.
>
>
>
>
>
> Type referenced: nt!_LIST_ENTRY
>
>
>
>
>
>
>
> Unable to read _LIST_ENTRY @ 808ad0c8
>
>
> ________________________________
>
>
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> Ramaraj Pandian
> Sent: Monday, July 02, 2007 3:36 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Your debugger is not using the correct symbols
>
>
>
> I was debugging happily for long time with pointing MS web symbol server.
>
> But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
> debug and it always complains about “not using correct symbols”
>
>
>
> This is the output I get for “lm lv”:
>
>
>
> 0: kd> lm lv
>
> start end module name
>
> 80800000 80a56000 nt (pdb symbols)
> .\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb
>
> Loaded symbol image file: ntkrpamp.exe
>
> Image path: ntkrpamp.exe
>
> Image name: ntkrpamp.exe
>
> Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)
>
> CheckSum: 0023D8B4
>
> ImageSize: 00256000
>
> File version: 5.2.3790.2825
>
> Product version: 5.2.3790.2825
>
> File flags: 0 (Mask 3F)
>
> File OS: 40004 NT Win32
>
> File type: 1.0 App
>
> File date: 00000000.00000000
>
> Translations: 0409.04b0
>
> CompanyName: Microsoft Corporation
>
> ProductName: Microsoft(r) Windows(r) Operating System
>
> InternalName: ntkrpamp.exe
>
> OriginalFilename: ntkrpamp.exe
>
> ProductVersion: 5.2.3790.2825
>
> FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)
>
> FileDescription: NT Kernel & System
>
> LegalCopyright: (c) Microsoft Corporation. All rights reserved.
>
>
>
> Could you guys shed some light?
>
> Thanks
>
> Ramaraj
>
>
>
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com

6

Thanks for your reply.

Answer your questions:

  • I am getting all symbols from MS web server.

  • This is what I get with lml and it is correct

" 0: kd> !sym noisy

noisy mode - symbol prompts on

0: kd> lml

start end module name

80800000 80a56000 nt (pdb symbols)
.\memory.b34-websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\n
tkrpamp.pdb"

  • I will try what you suggested to build LIST_ENTRY

  • There is no symbol package for windows 2003 R2 SP2. I
    downloaded SP2 package but same problem.

  • I am using free build of OS not Checked build.

Thanks

Ramaraj

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, July 03, 2007 5:04 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Your debugger is not using the correct symbols

Is the only error? If so, it looks like one of those cases where a type
(_LIST_ENTRY) got stripped and shouldn’t have before Microsoft shipped
the symbol file. That being said, I can’t say that I know what
‘websymbols,’ which makes me curious. Are you getting these from
http://msdl.microsoft.com/download/symbols and !sym noisy followed by
lml looks ok?

Assuming that you are in fact already loading the best matching
symbols, I can tell you (roughly) how to resolve this specific error.

  1. Create a header file with the definition of _LIST_ENTRY in it.

  2. Compile it with (among other switches) -Fp -TC, replacing
    with the fullpath of the file WinDbg is loading for ntoskrnl symbols.
    The -TC just compiles an H file as C.

    This will add the type _LIST_ENTRY which !process apparently needs.

    The other thing that I would recommend doing is checking this link
    (http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx) to see
    if the symbol package can be downloaded. I’ve had a couple of
    experiences where the symbol server had either incorrect or no symbols
    and this page did.

    I don’t know if this still happens, but a while back, in my opinion,
    Microsoft not commonly did not release symbols for some of the more
    esoteric os and service packs, particularly for checked builds. I don’t
    know if 2003 R2 falls in to the category, but I have never come across
    it.

    Good luck,

    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Tuesday, July 03, 2007 19:45
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] Your debugger is not using the correct symbols

    I tried clearing/reloading/overwriting, etc. But I get same error. Could
    somebody help me out of this? Thanks.

    This is what I get when I do !process

    0: kd> !process 0 7

    NT ACTIVE PROCESS DUMP










    Your debugger is not using the correct symbols


    In order for this command to work properly, your symbol path


     must point to .pdb files that have full type information.


    Certain .pdb files (such as the public OS symbols) do not


     contain the required information. Contact the group that


     provided you with these symbols if you need this command to


     work.


    Type referenced: nt!_LIST_ENTRY


    *
    *

    Unable to read _LIST_ENTRY @ 808ad0c8



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Monday, July 02, 2007 3:36 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Your debugger is not using the correct symbols

    I was debugging happily for long time with pointing MS web symbol
    server.

    But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
    debug and it always complains about “not using correct symbols”

    This is the output I get for “lm lv”:

    0: kd> lm lv

    start end module name

    80800000 80a56000 nt (pdb symbols)
    .\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

    Loaded symbol image file: ntkrpamp.exe

    Image path: ntkrpamp.exe

    Image name: ntkrpamp.exe

    Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

    CheckSum: 0023D8B4

    ImageSize: 00256000

    File version: 5.2.3790.2825

    Product version: 5.2.3790.2825

    File flags: 0 (Mask 3F)

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0409.04b0

    CompanyName: Microsoft Corporation

    ProductName: Microsoft(r) Windows(r) Operating System

    InternalName: ntkrpamp.exe

    OriginalFilename: ntkrpamp.exe

    ProductVersion: 5.2.3790.2825

    FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

    FileDescription: NT Kernel & System

    LegalCopyright: (c) Microsoft Corporation. All rights reserved.

    Could you guys shed some light?

    Thanks

    Ramaraj

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

7

Are you trying this on SP2 RTM?

B7D3B775988A4F06BF8B82530337AC831 seems to correspond
to a pre-release version of SP2 - more precisely, 5.2.3790.2825
(srv03_sp2_rc.061103-1303).

–
This posting is provided “AS IS” with no warranties, and confers no
rights.

8

I hope what I suggested helps. This symbols path is so damn strange, I
wouldn’t expect a great deal of standard functionality. It almost looks
like a beta version.

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
Sent: Thursday, July 05, 2007 13:46
To: Kernel Debugging Interest List
Subject: RE: [windbg] Your debugger is not using the correct symbols

Thanks for your reply.

Answer your questions:

  • I am getting all symbols from MS web server.

  • This is what I get with lml and it is correct

" 0: kd> !sym noisy

noisy mode - symbol prompts on

0: kd> lml

start end module name

80800000 80a56000 nt (pdb symbols)
.\memory.b34-websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\n
tkrpamp.pdb"

  • I will try what you suggested to build LIST_ENTRY

  • There is no symbol package for windows 2003 R2 SP2. I
    downloaded SP2 package but same problem.

  • I am using free build of OS not Checked build.

Thanks

Ramaraj

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, July 03, 2007 5:04 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Your debugger is not using the correct symbols

Is the only error? If so, it looks like one of those cases where a type
(_LIST_ENTRY) got stripped and shouldn’t have before Microsoft shipped
the symbol file. That being said, I can’t say that I know what
‘websymbols,’ which makes me curious. Are you getting these from
http://msdl.microsoft.com/download/symbols and !sym noisy followed by
lml looks ok?

Assuming that you are in fact already loading the best matching
symbols, I can tell you (roughly) how to resolve this specific error.

  1. Create a header file with the definition of _LIST_ENTRY in it.

  2. Compile it with (among other switches) -Fp -TC, replacing
    with the fullpath of the file WinDbg is loading for ntoskrnl symbols.
    The -TC just compiles an H file as C.

    This will add the type _LIST_ENTRY which !process apparently needs.

    The other thing that I would recommend doing is checking this link
    (http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx) to see
    if the symbol package can be downloaded. I’ve had a couple of
    experiences where the symbol server had either incorrect or no symbols
    and this page did.

    I don’t know if this still happens, but a while back, in my opinion,
    Microsoft not commonly did not release symbols for some of the more
    esoteric os and service packs, particularly for checked builds. I don’t
    know if 2003 R2 falls in to the category, but I have never come across
    it.

    Good luck,

    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Tuesday, July 03, 2007 19:45
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] Your debugger is not using the correct symbols

    I tried clearing/reloading/overwriting, etc. But I get same error. Could
    somebody help me out of this? Thanks.

    This is what I get when I do !process

    0: kd> !process 0 7

    NT ACTIVE PROCESS DUMP










    Your debugger is not using the correct symbols


    In order for this command to work properly, your symbol path


     must point to .pdb files that have full type information.


    Certain .pdb files (such as the public OS symbols) do not


     contain the required information. Contact the group that


     provided you with these symbols if you need this command to


     work.


    Type referenced: nt!_LIST_ENTRY


    *
    *

    Unable to read _LIST_ENTRY @ 808ad0c8



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Ramaraj Pandian
    Sent: Monday, July 02, 2007 3:36 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Your debugger is not using the correct symbols

    I was debugging happily for long time with pointing MS web symbol
    server.

    But after “Windows 2003 R2 SP2” upgrade of test m/c, I could not able to
    debug and it always complains about “not using correct symbols”

    This is the output I get for “lm lv”:

    0: kd> lm lv

    start end module name

    80800000 80a56000 nt (pdb symbols)
    .\websymbols\ntkrpamp.pdb\B7D3B775988A4F06BF8B82530337AC831\ntkrpamp.pdb

    Loaded symbol image file: ntkrpamp.exe

    Image path: ntkrpamp.exe

    Image name: ntkrpamp.exe

    Timestamp: Fri Nov 03 19:15:48 2006 (454BF7D4)

    CheckSum: 0023D8B4

    ImageSize: 00256000

    File version: 5.2.3790.2825

    Product version: 5.2.3790.2825

    File flags: 0 (Mask 3F)

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0409.04b0

    CompanyName: Microsoft Corporation

    ProductName: Microsoft(r) Windows(r) Operating System

    InternalName: ntkrpamp.exe

    OriginalFilename: ntkrpamp.exe

    ProductVersion: 5.2.3790.2825

    FileVersion: 5.2.3790.2825 (srv03_sp2_rc.061103-1303)

    FileDescription: NT Kernel & System

    LegalCopyright: (c) Microsoft Corporation. All rights reserved.

    Could you guys shed some light?

    Thanks

    Ramaraj

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com

    —
    You are currently subscribed to windbg as: unknown lmsubst tag argument:
    ‘’
    To unsubscribe send a blank email to xxxxx@lists.osr.com