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

Home NTDEV

Before Posting...

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

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/


Re: Windbg

Mark_S._EdwardsMark_S._Edwards Member Posts: 475
At 04:31 PM 1/21/2000 -0800, Lee Fisher wrote:
>yes, we're aware of the problems with Windbg. and we're taking some major
>steps to improve it. we've currently hard at work to release an improved
>version of Windbg (and NTSD/KD).

<snip>

> as
>soon as we've a release of this debugger package which is publicly usable,
>i'll send out notice.
>
>Lee

Has anybody heard anything more on this topic, it's been 3 months since Lee
said MS were working on it. Apologies if I missed the announcement.

Mark

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Haven't you noticed that windbag has improved? My copy has. Oh well, maybe
    its just that windbag has trained me to work 'the windbag way'. (The Tao of
    Windbag. :-)

    I never try to use workspaces anymore. Do everything from the command line
    instead.

    I never do any prolonged output commands (!process 0 7 is a no no.)

    I always save command window information before I do anything, as that may
    be the last time I get a chance to record the session.

    Given a choice, windbag prefers nt4 over w2k.

    Breakpoints are problematic, so add lots of printf tracing as an
    alternative.

    I have actually gotten used to the miserable state of affairs.

    > -----Original Message-----
    > From: Mark S. Edwards [mailto:[email protected]]
    > Sent: Friday, March 31, 2000 8:35 AM
    > To: NT Developers Interest List
    > Subject: [ntdev] Re: Windbg
    >
    >
    > At 04:31 PM 1/21/2000 -0800, Lee Fisher wrote:
    > >yes, we're aware of the problems with Windbg. and we're
    > taking some major
    > >steps to improve it. we've currently hard at work to release
    > an improved
    > >version of Windbg (and NTSD/KD).
    >
    > <snip>
    >
    > > as
    > >soon as we've a release of this debugger package which is
    > publicly usable,
    > >i'll send out notice.
    > >
    > >Lee
    >
    > Has anybody heard anything more on this topic, it's been 3
    > months since Lee
    > said MS were working on it. Apologies if I missed the announcement.
    >
    > Mark
    >
    >
    > ---
    > You are currently subscribed to ntdev as: [email protected]
    > To unsubscribe send a blank email to $subst('Email.Unsub')
    >
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I can not wait for any announcement from MS relating to improvement or bug
    fixing, so I have changed the front to softice. This is not an advertisement
    for Compuware.
    It seems to me that Compuware imitates MS, to misuse the monopol to be
    great. Because in order to have softice we must buy additional 3 other
    tools, which do not have to do with debugging.
    For short the situation on device driver debugging on Win2K: the BIG
    monopolist is helping the SMALL one.

    But there is always a hope for us, the device driver's software developer,
    the use of DbgPrint() and a properly designed device driver, so that we are
    free from any Debugger.


    > ----------
    > From: Roddy, Mark[SMTP:[email protected]]
    > Reply To: NT Developers Interest List
    > Sent: Friday, March 31, 2000 4:39 PM
    > To: NT Developers Interest List
    > Subject: [ntdev] Re: Windbg
    >
    > Haven't you noticed that windbag has improved? My copy has. Oh well, maybe
    > its just that windbag has trained me to work 'the windbag way'. (The Tao
    > of
    > Windbag. :-)
    >
    > I never try to use workspaces anymore. Do everything from the command line
    > instead.
    >
    > I never do any prolonged output commands (!process 0 7 is a no no.)
    >
    > I always save command window information before I do anything, as that may
    > be the last time I get a chance to record the session.
    >
    > Given a choice, windbag prefers nt4 over w2k.
    >
    > Breakpoints are problematic, so add lots of printf tracing as an
    > alternative.
    >
    > I have actually gotten used to the miserable state of affairs.
    >
    > > -----Original Message-----
    > > From: Mark S. Edwards [mailto:[email protected]]
    > > Sent: Friday, March 31, 2000 8:35 AM
    > > To: NT Developers Interest List
    > > Subject: [ntdev] Re: Windbg
    > >
    > >
    > > At 04:31 PM 1/21/2000 -0800, Lee Fisher wrote:
    > > >yes, we're aware of the problems with Windbg. and we're
    > > taking some major
    > > >steps to improve it. we've currently hard at work to release
    > > an improved
    > > >version of Windbg (and NTSD/KD).
    > >
    > > <snip>
    > >
    > > > as
    > > >soon as we've a release of this debugger package which is
    > > publicly usable,
    > > >i'll send out notice.
    > > >
    > > >Lee
    > >
    > > Has anybody heard anything more on this topic, it's been 3
    > > months since Lee
    > > said MS were working on it. Apologies if I missed the announcement.
    > >
    > > Mark
    > >
    > >
    > > ---
    > > You are currently subscribed to ntdev as: [email protected]
    > > To unsubscribe send a blank email to $subst('Email.Unsub')
    > >
    >
    > ---
    > You are currently subscribed to ntdev as: [email protected]
    > To unsubscribe send a blank email to $subst('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!
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online
Writing WDF Drivers 12 September 2022 Live, Online