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

Home› WINDBG

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/


WinDbg ~ Command

OSR_Community_User-158OSR_Community_User-158 Member Posts: 6
in WINDBG
Hello,

I am new to WinDbg and am using it to debug my Win2K Bus Driver on an MP
System. After I press in WinDbg, ~ command shows the following
output:

* 0 1 Stopped 0xFFFFFFFFFFDFF800
1 2 Running 0x...
2 3 Running 0x...
3 4 Running 0x...

Does this mean that ONLY the thread on CPU 0 is stopped (and the threads on
CPU 1, 2 and 3 are running) ?

OR

All the threads are stopped/CPUs are stopped ?

What does the address 0xFFFFFFFFFFDFF800 mean ?

Is there any way to know which debug printf messages are coming from which
CPUs ?

Thanks
Puja
· Share on Facebook

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    0xFF.. is 64-bit ready. Ignore the first 8 Fs.

    Yes, there is just one thread stopped. The rest is running.



    ----- Original Message -----
    From: <[email protected]>
    To: "Kernel Debugging Interest List" <[email protected]>
    Sent: Monday, May 15, 2000 9:14 PM
    Subject: [windbg] WinDbg ~ Command


    > Hello,
    >
    > I am new to WinDbg and am using it to debug my Win2K Bus Driver on an MP
    > System. After I press <ctrl+C> in WinDbg, ~ command shows the following
    > output:
    >
    > * 0 1 Stopped 0xFFFFFFFFFFDFF800
    > 1 2 Running 0x...
    > 2 3 Running 0x...
    > 3 4 Running 0x...
    >
    > Does this mean that ONLY the thread on CPU 0 is stopped (and the threads
    on
    > CPU 1, 2 and 3 are running) ?
    >
    > OR
    >
    > All the threads are stopped/CPUs are stopped ?
    >
    > What does the address 0xFFFFFFFFFFDFF800 mean ?
    >
    > Is there any way to know which debug printf messages are coming from which
    > CPUs ?
    >
    > Thanks
    > Puja
    >
    >
    > ---
    > You are currently subscribed to windbg as: [email protected]
    > To unsubscribe send a blank email to $subst('Email.Unsub')
    >
    · Share on Facebook
Sign In or Register to comment.

Howdy, Stranger!

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

Sign In Register
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 19-23 June 2023 Live, Online
Writing WDF Drivers 10-14 July 2023 Live, Online
Kernel Debugging 16-20 October 2023 Live, Online
Developing Minifilters 13-17 November 2023 Live, Online

Categories