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.

Setup Win XP host and Win 2000 target?

Henrik_BechHenrik_Bech Member Posts: 2
I am not too experienced in windbg and need some help.

After updating the system to Windows XP with Visual Studio .NET and windbg
4.00.18 I have trouble getting the debug session to run.

The symbol path is set to the win 2000 symbol directory installed on the
host.

After a series of ModLoad og XP ddls the debugger stops with:
*** WARNING: symbols timestamp is wrong 0x3b7de01e 0x3af32050 for
ntdll.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntdll.dll -
ntdll!DbgBreakPoint:
77f7f570 cc int 3

Thanks
Henrik Bech

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Try using the command "!sym noisy" - this will show you where the debugger
    is searching for symbols.

    You can also achieve the same thing by starting WinDBG with the "-sflags
    0x80030237" option (see the documentation for a description of the various
    symbol options).

    Of course, you can always try the current version of the debugger as well -
    the current version is 6.0.7.

    Regards,

    Tony

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


    -----Original Message-----
    From: [email protected] [mailto:[email protected]]
    Sent: Thursday, March 14, 2002 5:07 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] Setup Win XP host and Win 2000 target?

    I am not too experienced in windbg and need some help.

    After updating the system to Windows XP with Visual Studio .NET and windbg
    4.00.18 I have trouble getting the debug session to run.

    The symbol path is set to the win 2000 symbol directory installed on the
    host.

    After a series of ModLoad og XP ddls the debugger stops with:
    *** WARNING: symbols timestamp is wrong 0x3b7de01e 0x3af32050 for
    ntdll.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols
    for ntdll.dll -
    ntdll!DbgBreakPoint:
    77f7f570 cc int 3

    Thanks
    Henrik Bech

    ---
    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
    It seems like you use the wrong symbols.
    Check which win2k SP you use and match it to
    the symbol pack.
    (in case you use win2k SP2 you might need to
    download additional symbols installation file for
    SP2)
    In case the above won't work, I think you should
    try MS symbol server, to do it paste the below under
    the symbol path
    srv*c:\symbols*http://msdl.microsoft.com/download/symbol

    -Mike.

    --- Tony Mason <[email protected]> wrote:
    > Try using the command "!sym noisy" - this will show
    > you where the debugger
    > is searching for symbols.
    >
    > You can also achieve the same thing by starting
    > WinDBG with the "-sflags
    > 0x80030237" option (see the documentation for a
    > description of the various
    > symbol options).
    >
    > Of course, you can always try the current version of
    > the debugger as well -
    > the current version is 6.0.7.
    >
    > Regards,
    >
    > Tony
    >
    > Tony Mason
    > Consulting Partner
    > OSR Open Systems Resources, Inc.
    > http://www.osr.com
    >
    >
    > -----Original Message-----
    > From: [email protected] [mailto:[email protected]]
    > Sent: Thursday, March 14, 2002 5:07 AM
    > To: Kernel Debugging Interest List
    > Subject: [windbg] Setup Win XP host and Win 2000
    > target?
    >
    > I am not too experienced in windbg and need some
    > help.
    >
    > After updating the system to Windows XP with Visual
    > Studio .NET and windbg
    > 4.00.18 I have trouble getting the debug session to
    > run.
    >
    > The symbol path is set to the win 2000 symbol
    > directory installed on the
    > host.
    >
    > After a series of ModLoad og XP ddls the debugger
    > stops with:
    > *** WARNING: symbols timestamp is wrong 0x3b7de01e
    > 0x3af32050 for
    > ntdll.dll
    > *** ERROR: Symbol file could not be found.
    > Defaulted to export symbols
    > for ntdll.dll -
    > ntdll!DbgBreakPoint:
    > 77f7f570 cc int 3
    >
    > Thanks
    > Henrik Bech
    >
    > ---
    > 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%%


    __________________________________________________
    Do You Yahoo!?
    Yahoo! Sports - live college hoops coverage
    http://sports.yahoo.com/
  • Nathan_NesbitNathan_Nesbit Member Posts: 194
    Adding "-n" to the command line of any of the debuggers that ship in the
    package will turn on noisy symbol loading. It's a tad bit easier to
    type than -sflags....

    -----Original Message-----
    From: Tony Mason [mailto:[email protected]]
    Sent: Thursday, March 14, 2002 3:27 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Setup Win XP host and Win 2000 target?


    Try using the command "!sym noisy" - this will show you where the
    debugger is searching for symbols.

    You can also achieve the same thing by starting WinDBG with the "-sflags
    0x80030237" option (see the documentation for a description of the
    various symbol options).

    Of course, you can always try the current version of the debugger as
    well - the current version is 6.0.7.

    Regards,

    Tony

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


    -----Original Message-----
    From: [email protected] [mailto:[email protected]]
    Sent: Thursday, March 14, 2002 5:07 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] Setup Win XP host and Win 2000 target?

    I am not too experienced in windbg and need some help.

    After updating the system to Windows XP with Visual Studio .NET and
    windbg 4.00.18 I have trouble getting the debug session to run.

    The symbol path is set to the win 2000 symbol directory installed on the
    host.

    After a series of ModLoad og XP ddls the debugger stops with:
    *** WARNING: symbols timestamp is wrong 0x3b7de01e 0x3af32050 for
    ntdll.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols
    for ntdll.dll -
    ntdll!DbgBreakPoint:
    77f7f570 cc int 3

    Thanks
    Henrik Bech

    ---
    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%%
  • http://msdl.microsoft.com/download/symbol is really avairable?

    Thanks
    Kimi

    -----Original Message-----
    From: Mike Malgin [mailto:[email protected]]
    Sent: Thursday, March 14, 2002 8:48 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] RE: Setup Win XP host and Win 2000 target?



    It seems like you use the wrong symbols.
    Check which win2k SP you use and match it to
    the symbol pack.
    (in case you use win2k SP2 you might need to
    download additional symbols installation file for
    SP2)
    In case the above won't work, I think you should
    try MS symbol server, to do it paste the below under
    the symbol path srv*c:\symbols*http://msdl.microsoft.com/download/symbol

    -Mike.

    --- Tony Mason <[email protected]> wrote:
    > Try using the command "!sym noisy" - this will show
    > you where the debugger
    > is searching for symbols.
    >
    > You can also achieve the same thing by starting
    > WinDBG with the "-sflags
    > 0x80030237" option (see the documentation for a
    > description of the various
    > symbol options).
    >
    > Of course, you can always try the current version of
    > the debugger as well -
    > the current version is 6.0.7.
    >
    > Regards,
    >
    > Tony
    >
    > Tony Mason
    > Consulting Partner
    > OSR Open Systems Resources, Inc.
    > http://www.osr.com
    >
    >
    > -----Original Message-----
    > From: [email protected] [mailto:[email protected]]
    > Sent: Thursday, March 14, 2002 5:07 AM
    > To: Kernel Debugging Interest List
    > Subject: [windbg] Setup Win XP host and Win 2000
    > target?
    >
    > I am not too experienced in windbg and need some
    > help.
    >
    > After updating the system to Windows XP with Visual
    > Studio .NET and windbg
    > 4.00.18 I have trouble getting the debug session to
    > run.
    >
    > The symbol path is set to the win 2000 symbol
    > directory installed on the
    > host.
    >
    > After a series of ModLoad og XP ddls the debugger
    > stops with:
    > *** WARNING: symbols timestamp is wrong 0x3b7de01e
    > 0x3af32050 for
    > ntdll.dll
    > *** ERROR: Symbol file could not be found.
    > Defaulted to export symbols
    > for ntdll.dll -
    > ntdll!DbgBreakPoint:
    > 77f7f570 cc int 3
    >
    > Thanks
    > Henrik Bech
    >
    > ---
    > 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%%


    __________________________________________________
    Do You Yahoo!?
    Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/

    ---
    You are currently subscribed to windbg as: [email protected] To
    unsubscribe send a blank email to %%email.unsub%%
  • Alan-2Alan-2 Member Posts: 9
    It's really http://msdl.microsoft.com/download/symbols (with final 's')
    Alan

    wrote in message news:[email protected]
    >
    > http://msdl.microsoft.com/download/symbol is really avairable?
    >
    > Thanks
    > Kimi
    >
    > -----Original Message-----
    > From: Mike Malgin [mailto:[email protected]]
    > Sent: Thursday, March 14, 2002 8:48 PM
    > To: Kernel Debugging Interest List
    > Subject: [windbg] RE: Setup Win XP host and Win 2000 target?
    >
    >
    >
    > It seems like you use the wrong symbols.
    > Check which win2k SP you use and match it to
    > the symbol pack.
    > (in case you use win2k SP2 you might need to
    > download additional symbols installation file for
    > SP2)
    > In case the above won't work, I think you should
    > try MS symbol server, to do it paste the below under
    > the symbol path srv*c:\symbols*http://msdl.microsoft.com/download/symbol
    >
    > -Mike.
    >
    > --- Tony Mason wrote:
    > > Try using the command "!sym noisy" - this will show
    > > you where the debugger
    > > is searching for symbols.
    > >
    > > You can also achieve the same thing by starting
    > > WinDBG with the "-sflags
    > > 0x80030237" option (see the documentation for a
    > > description of the various
    > > symbol options).
    > >
    > > Of course, you can always try the current version of
    > > the debugger as well -
    > > the current version is 6.0.7.
    > >
    > > Regards,
    > >
    > > Tony
    > >
    > > Tony Mason
    > > Consulting Partner
    > > OSR Open Systems Resources, Inc.
    > > http://www.osr.com
    > >
    > >
    > > -----Original Message-----
    > > From: [email protected] [mailto:[email protected]]
    > > Sent: Thursday, March 14, 2002 5:07 AM
    > > To: Kernel Debugging Interest List
    > > Subject: [windbg] Setup Win XP host and Win 2000
    > > target?
    > >
    > > I am not too experienced in windbg and need some
    > > help.
    > >
    > > After updating the system to Windows XP with Visual
    > > Studio .NET and windbg
    > > 4.00.18 I have trouble getting the debug session to
    > > run.
    > >
    > > The symbol path is set to the win 2000 symbol
    > > directory installed on the
    > > host.
    > >
    > > After a series of ModLoad og XP ddls the debugger
    > > stops with:
    > > *** WARNING: symbols timestamp is wrong 0x3b7de01e
    > > 0x3af32050 for
    > > ntdll.dll
    > > *** ERROR: Symbol file could not be found.
    > > Defaulted to export symbols
    > > for ntdll.dll -
    > > ntdll!DbgBreakPoint:
    > > 77f7f570 cc int 3
    > >
    > > Thanks
    > > Henrik Bech
    > >
    > > ---
    > > 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%%
    >
    >
    > __________________________________________________
    > Do You Yahoo!?
    > Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/
    >
    > ---
    > You are currently subscribed to windbg as: [email protected] To
    > unsubscribe send a blank email to %%email.unsub%%
    >
    >
  • OK, Thank you very much. Now works properly :-) "s" is important.

    Kimi

    -----Original Message-----
    From: Alan Hodges [mailto:[email protected]]
    Sent: Friday, March 15, 2002 3:08 PM
    To: Kernel Debugging Interest List
    Subject: [windbg] Re: Setup Win XP host and Win 2000 target?


    It's really http://msdl.microsoft.com/download/symbols (with final 's')
    Alan

    <[email protected]> wrote in message news:[email protected]
    >
    > http://msdl.microsoft.com/download/symbol is really avairable?
    >
    > Thanks
    > Kimi
    >
    > -----Original Message-----
    > From: Mike Malgin [mailto:[email protected]]
    > Sent: Thursday, March 14, 2002 8:48 PM
    > To: Kernel Debugging Interest List
    > Subject: [windbg] RE: Setup Win XP host and Win 2000 target?
    >
    >
    >
    > It seems like you use the wrong symbols.
    > Check which win2k SP you use and match it to
    > the symbol pack.
    > (in case you use win2k SP2 you might need to
    > download additional symbols installation file for
    > SP2)
    > In case the above won't work, I think you should
    > try MS symbol server, to do it paste the below under
    > the symbol path srv*c:\symbols*http://msdl.microsoft.com/download/symbol
    >
    > -Mike.
    >
    > --- Tony Mason <[email protected]> wrote:
    > > Try using the command "!sym noisy" - this will show
    > > you where the debugger
    > > is searching for symbols.
    > >
    > > You can also achieve the same thing by starting
    > > WinDBG with the "-sflags
    > > 0x80030237" option (see the documentation for a
    > > description of the various
    > > symbol options).
    > >
    > > Of course, you can always try the current version of
    > > the debugger as well -
    > > the current version is 6.0.7.
    > >
    > > Regards,
    > >
    > > Tony
    > >
    > > Tony Mason
    > > Consulting Partner
    > > OSR Open Systems Resources, Inc.
    > > http://www.osr.com
    > >
    > >
    > > -----Original Message-----
    > > From: [email protected] [mailto:[email protected]]
    > > Sent: Thursday, March 14, 2002 5:07 AM
    > > To: Kernel Debugging Interest List
    > > Subject: [windbg] Setup Win XP host and Win 2000
    > > target?
    > >
    > > I am not too experienced in windbg and need some
    > > help.
    > >
    > > After updating the system to Windows XP with Visual
    > > Studio .NET and windbg
    > > 4.00.18 I have trouble getting the debug session to
    > > run.
    > >
    > > The symbol path is set to the win 2000 symbol
    > > directory installed on the
    > > host.
    > >
    > > After a series of ModLoad og XP ddls the debugger
    > > stops with:
    > > *** WARNING: symbols timestamp is wrong 0x3b7de01e
    > > 0x3af32050 for
    > > ntdll.dll
    > > *** ERROR: Symbol file could not be found.
    > > Defaulted to export symbols
    > > for ntdll.dll -
    > > ntdll!DbgBreakPoint:
    > > 77f7f570 cc int 3
    > >
    > > Thanks
    > > Henrik Bech
    > >
    > > ---
    > > 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%%
    >
    >
    > __________________________________________________
    > Do You Yahoo!?
    > Yahoo! Sports - live college hoops coverage http://sports.yahoo.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%%
  • Henrik_BechHenrik_Bech Member Posts: 2
    Thanks for the input. Unfortunally it did not help so far.

    The symbols are installed from the same DVD as the target OS (both Win
    2000, SP2 checked).

    Now I have downloaded windbg 6.0.7 and will give it a try.

    I have used ver 3 of windbg without any problems, but will invest some
    time to learn to use the new version.

    Henrik
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