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

0xFF… is 64-bit ready. Ignore the first 8 Fs.

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

----- Original Message -----
From:
To: “Kernel Debugging Interest List”
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 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: xxxxx@intelligraphics.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>