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

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

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 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

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')
    >
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE