Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Local kernel debugging with 6.0.7 on XP

OSR_Community_UserOSR_Community_User Member Posts: 110,217
Are there any known issues when using 6.0.7 on XP in a local kernel debug
situation? I have a machine here that merely reports back "Unable to get
address of debugger data list". The symbols appear to be correct (starting
it with -n, no reports that it even LOOKS for any symbols.) I tried
".reload" but that merely repeats this error. I've also run symchk to make
sure I have the right symbols - it reports that I have them for
ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Hi Tony,

    Are you using a symbol server? The problem I have encountered with
    symbol server is that the debugger has difficulties to both use the
    symbols on the symbol server and the local path for your own modules.

    Best regards,
    Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]

    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Wednesday, March 20, 2002 7:20 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Local kernel debugging with 6.0.7 on XP


    Are there any known issues when using 6.0.7 on XP in a local kernel
    debug situation? I have a machine here that merely reports back "Unable
    to get address of debugger data list". The symbols appear to be correct
    (starting it with -n, no reports that it even LOOKS for any symbols.) I
    tried ".reload" but that merely repeats this error. I've also run
    symchk to make sure I have the right symbols - it reports that I have
    them for ntoskrnl.exe.

    Another machine I have here works fine with it.

    Thoughts? Suggestions? Ideas?

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com


    ---
    You are currently subscribed to windbg as: [email protected]

    To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Marco,

    Thanks for your suggestion.

    As it turns out, you must set the /debug option in boot.ini even for local
    debugging. The fact that it worked on my laptop (which has lots of memory)
    and not on the machine I was using (hooked up to a projector that I was
    using for the presentation) was fortuitous.

    Of course, the solution was simple - I just started a server session on my
    laptop and connected to it on the other computer (thus, I was running a
    remote kernel debug session on a system doing local debugging!)

    As for the symbol server, the "symchk" utility included in the Version 6.0.7
    debugger is a terrific way to "seed" the symbol cache so that I have
    everything I need (no need for the network). I have not observed the
    debugger having problems mixing sources of symbols, however.

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 4:19 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    Are you using a symbol server? The problem I have encountered with symbol
    server is that the debugger has difficulties to both use the symbols on the
    symbol server and the local path for your own modules.

    Best regards,
    Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]
    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Wednesday, March 20, 2002 7:20 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Local kernel debugging with 6.0.7 on XP
    Are there any known issues when using 6.0.7 on XP in a local kernel debug
    situation? I have a machine here that merely reports back "Unable to get
    address of debugger data list". The symbols appear to be correct (starting
    it with -n, no reports that it even LOOKS for any symbols.) I tried
    ".reload" but that merely repeats this error. I've also run symchk to make
    sure I have the right symbols - it reports that I have them for
    ntoskrnl.exe.

    Another machine I have here works fine with it.

    Thoughts? Suggestions? Ideas?

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com


    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Hi Tony,

    At the moment I have a problem debugging one of our InteroOp testing
    combinations. We do kernel mode debugging on a 115200 serial connection
    (and that is very slow!). So we tried to run dbgview.exe in client
    server mode but in that situation we are missing quite a lot of debug
    lines. The problem is that we cannot use WindowsXP for some InterOp
    testing because the real BSOD only occurs on Win2K or NT. We also had an
    idea on re-directing the info from dbgprint to a file on the harddisk
    but then we have the problem that we have both the driver and the
    service logging and having the risk that logging gets out of sync. Also
    the other challenge is to write to a file from within the driver
    itselves but we find that too tricky.

    You just describe a server session on the laptop, do you use DbgView or
    something else . ..

    grtx Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]


    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Thursday, March 21, 2002 1:56 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP


    Marco,

    Thanks for your suggestion.

    As it turns out, you must set the /debug option in boot.ini even for
    local debugging. The fact that it worked on my laptop (which has lots
    of memory) and not on the machine I was using (hooked up to a projector
    that I was using for the presentation) was fortuitous.

    Of course, the solution was simple - I just started a server session on
    my laptop and connected to it on the other computer (thus, I was running
    a remote kernel debug session on a system doing local debugging!)

    As for the symbol server, the "symchk" utility included in the Version
    6.0.7 debugger is a terrific way to "seed" the symbol cache so that I
    have everything I need (no need for the network). I have not observed
    the debugger having problems mixing sources of symbols, however.

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven
    [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 4:19 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    Are you using a symbol server? The problem I have encountered with
    symbol server is that the debugger has difficulties to both use the
    symbols on the symbol server and the local path for your own modules.

    Best regards,
    Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]
    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Wednesday, March 20, 2002 7:20 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Local kernel debugging with 6.0.7 on XP
    Are there any known issues when using 6.0.7 on XP in a local kernel
    debug situation? I have a machine here that merely reports back "Unable
    to get address of debugger data list". The symbols appear to be correct
    (starting it with -n, no reports that it even LOOKS for any symbols.) I
    tried ".reload" but that merely repeats this error. I've also run
    symchk to make sure I have the right symbols - it reports that I have
    them for ntoskrnl.exe.

    Another machine I have here works fine with it.

    Thoughts? Suggestions? Ideas?

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com


    ---
    You are currently subscribed to windbg as: [email protected]

    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I'm running WinDBG (local) on an XP system. That will not work on NT or
    W2K, so I fear that it will not solve your problem. Sorry!

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 8:15 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    At the moment I have a problem debugging one of our InteroOp testing
    combinations. We do kernel mode debugging on a 115200 serial connection (and
    that is very slow!). So we tried to run dbgview.exe in client server mode
    but in that situation we are missing quite a lot of debug lines. The problem
    is that we cannot use WindowsXP for some InterOp testing because the real
    BSOD only occurs on Win2K or NT. We also had an idea on re-directing the
    info from dbgprint to a file on the harddisk but then we have the problem
    that we have both the driver and the service logging and having the risk
    that logging gets out of sync. Also the other challenge is to write to a
    file from within the driver itselves but we find that too tricky.

    You just describe a server session on the laptop, do you use DbgView or
    something else . ..

    grtx Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]

    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Thursday, March 21, 2002 1:56 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP
    Marco,

    Thanks for your suggestion.

    As it turns out, you must set the /debug option in boot.ini even for local
    debugging. The fact that it worked on my laptop (which has lots of memory)
    and not on the machine I was using (hooked up to a projector that I was
    using for the presentation) was fortuitous.

    Of course, the solution was simple - I just started a server session on my
    laptop and connected to it on the other computer (thus, I was running a
    remote kernel debug session on a system doing local debugging!)

    As for the symbol server, the "symchk" utility included in the Version 6.0.7
    debugger is a terrific way to "seed" the symbol cache so that I have
    everything I need (no need for the network). I have not observed the
    debugger having problems mixing sources of symbols, however.

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 4:19 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    Are you using a symbol server? The problem I have encountered with symbol
    server is that the debugger has difficulties to both use the symbols on the
    symbol server and the local path for your own modules.

    Best regards,
    Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]
    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Wednesday, March 20, 2002 7:20 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Local kernel debugging with 6.0.7 on XP
    Are there any known issues when using 6.0.7 on XP in a local kernel debug
    situation? I have a machine here that merely reports back "Unable to get
    address of debugger data list". The symbols appear to be correct (starting
    it with -n, no reports that it even LOOKS for any symbols.) I tried
    ".reload" but that merely repeats this error. I've also run symchk to make
    sure I have the right symbols - it reports that I have them for
    ntoskrnl.exe.

    Another machine I have here works fine with it.

    Thoughts? Suggestions? Ideas?

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com


    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I was already afraid that was the case. Does anyone know if it is
    possible to use an other UART (like the 16650) which can run on 4 times
    115200Kb?

    grtx Marco.
    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Thursday, March 21, 2002 2:24 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP


    I'm running WinDBG (local) on an XP system. That will not work on NT or
    W2K, so I fear that it will not solve your problem. Sorry!

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven
    [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 8:15 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    At the moment I have a problem debugging one of our InteroOp testing
    combinations. We do kernel mode debugging on a 115200 serial connection
    (and that is very slow!). So we tried to run dbgview.exe in client
    server mode but in that situation we are missing quite a lot of debug
    lines. The problem is that we cannot use WindowsXP for some InterOp
    testing because the real BSOD only occurs on Win2K or NT. We also had an
    idea on re-directing the info from dbgprint to a file on the harddisk
    but then we have the problem that we have both the driver and the
    service logging and having the risk that logging gets out of sync. Also
    the other challenge is to write to a file from within the driver
    itselves but we find that too tricky.

    You just describe a server session on the laptop, do you use DbgView or
    something else . ..

    grtx Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]

    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Thursday, March 21, 2002 1:56 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP
    Marco,

    Thanks for your suggestion.

    As it turns out, you must set the /debug option in boot.ini even for
    local debugging. The fact that it worked on my laptop (which has lots
    of memory) and not on the machine I was using (hooked up to a projector
    that I was using for the presentation) was fortuitous.

    Of course, the solution was simple - I just started a server session on
    my laptop and connected to it on the other computer (thus, I was running
    a remote kernel debug session on a system doing local debugging!)

    As for the symbol server, the "symchk" utility included in the Version
    6.0.7 debugger is a terrific way to "seed" the symbol cache so that I
    have everything I need (no need for the network). I have not observed
    the debugger having problems mixing sources of symbols, however.

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com

    -----Original Message-----
    From: ThunderStore - Marco van Nieuwenhoven
    [mailto:[email protected]]
    Sent: Thursday, March 21, 2002 4:19 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

    Hi Tony,

    Are you using a symbol server? The problem I have encountered with
    symbol server is that the debugger has difficulties to both use the
    symbols on the symbol server and the local path for your own modules.

    Best regards,
    Marco.

    Marco van Nieuwenhoven, QA Manager
    ThunderStore B.V. - www.thunderstore.com
    Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
    [email protected]
    -----Original Message-----
    From: [email protected]
    [mailto:[email protected]] On Behalf Of Tony Mason
    Sent: Wednesday, March 20, 2002 7:20 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Local kernel debugging with 6.0.7 on XP
    Are there any known issues when using 6.0.7 on XP in a local kernel
    debug situation? I have a machine here that merely reports back "Unable
    to get address of debugger data list". The symbols appear to be correct
    (starting it with -n, no reports that it even LOOKS for any symbols.) I
    tried ".reload" but that merely repeats this error. I've also run
    symchk to make sure I have the right symbols - it reports that I have
    them for ntoskrnl.exe.

    Another machine I have here works fine with it.

    Thoughts? Suggestions? Ideas?

    Regards,

    Tony

    Tony Mason
    Consulting Partner
    OSR Open Systems Resources, Inc.
    http://www.osr.com


    ---
    You are currently subscribed to windbg as: [email protected]

    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
    ---
    You are currently subscribed to windbg as: [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online