Hi folks,
Is there any way to display the XMM registers in kernel mode in WinDBG? While I’ve managed to get the registers displayed but they do not contain the correct values.
Also, is there any way to change the formatting? They appear stuck in the 32bit float format.
Thanks.
-Rex.
I was able to display in the format of my preference using the below command:
r xmm#:type, xmm#:type e.g., r xmm0:uq, xmm1:iq will display xmm0 in unsigned quad and xmm1 in signed quad
However, I wasn’t able to set the format of my preference as default. BTW, WinDbg documentation has a list of types to choose from.
Kamala
-------------- Original message --------------
From: “Rex K. Perkins”
> Hi folks,
>
> Is there any way to display the XMM registers in kernel mode in WinDBG? While
> I’ve managed to get the registers displayed but they do not contain the correct
> values.
>
> Also, is there any way to change the formatting? They appear stuck in the 32bit
> float format.
>
> Thanks.
>
> -Rex.
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@comcast.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
Explicit r xmm#:type is the only way to display XMM registers in a non-default format. There is no way to set a general default, nor is there a way to influence the display of the registers in windbg’s registers window.
We have these kinds of things on our list for future consideration, but they are low priority.
From: xxxxx@lists.osr.com on behalf of xxxxx@comcast.net
Sent: Fri 2/10/2006 7:18 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] XMM registers in WinDBG?
I was able to display in the format of my preference using the below command:
r xmm#:type, xmm#:type e.g., r xmm0:uq, xmm1:iq will display xmm0 in unsigned quad and xmm1 in signed quad
However, I wasn’t able to set the format of my preference as default. BTW, WinDbg documentation has a list of types to choose from.
Kamala
-------------- Original message --------------
From: “Rex K. Perkins”
> Hi folks,
>
> Is there any way to display the XMM registers in kernel mode in WinDBG? While
> I’ve managed to get the registers displayed but they do not contain the correct
> values.
>
> Also, is there any way to change the formatting? They appear stuck in the 32bit
> float format.
>
> Thanks.
>
> -Rex.
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@comcast.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Please set that to Very High Priority.
Reason:
WinDbg is the only debugger available from Microsoft that can display mmx
registers in x64 64 bits. Why? Microsoft removed displaying of mmx registers
in x64 64 bits Visual 2005 Debugger. Why? Go figure? Then when we try to
debug x64 user applications that use mmx we can only use WinDbg to display
the mmx registers. Having a flexible way to format and display mmx or xmm
registers should be a requirement of Ring 3 debugging of WinDbg until
Microsoft provide with Visual 2005 displaying of mmx registers in a future
update.
Thanks
Guy
…
We have these kinds of things on our list for future consideration, but
they are low priority.
“Guy Bonneau” wrote in message news:xxxxx@windbg…
> Please set that to Very High Priority.
>
> Reason:
…
If this is so high priority for you, write an extension
to format xmms as you like?
–PA
Thanks Kamala and Drew.
I was hoping to change the formatting of the GUI, but doing it from
the command line is fine.
Armed with these commands I can now dump random values in the format
of my choice. Alas even the r command does not display the content of
the register in kernel mode. For example:
1: kd> df ebx+30 L4
e3b9e070 0 0.5 2 8
1: kd> r xmm4:f
xmm4=5.60519e-045 0 8.33893e-010 -1.34533
1: kd> p
e31cfeee 0f286330 movaps xmm4,oword ptr [ebx+0x30]
1: kd> p
…
1: kd> r xmm4:f
xmm4=5.60519e-045 0 8.33893e-010 -1.34533
The value of xmm4 clearly changed over that instruction (to the
values shown in df) but WinDBG didn’t see that.
Is there any solution to this?
Thanks.
-Rex.
Subject: RE: XMM registers in WinDBG?
From: “Drew Bliss”
>Date: Fri, 10 Feb 2006 10:03:22 -0800
>X-Message-Number: 5
>
>Explicit r xmm#:type is the only way to display XMM registers in a
>non-default format. There is no way to set a general default, nor
>is there a way to influence the display of the registers in windbg’s
>registers window.
>
>We have these kinds of things on our list for future consideration,
>but they are low priority.
>
> ________________________________
>
>From: xxxxx@lists.osr.com on behalf of
>xxxxx@comcast.net
>Sent: Fri 2/10/2006 7:18 AM
>To: Kernel Debugging Interest List
>Subject: Re: [windbg] XMM registers in WinDBG?
>
>
>
>I was able to display in the format of my preference using the below command:
>
>r xmm#:type, xmm#:type e.g., r xmm0:uq, xmm1:iq will display xmm0
>in unsigned quad and xmm1 in signed quad
>
>However, I wasn’t able to set the format of my preference as
>default. BTW, WinDbg documentation has a list of types to choose from.
>
>Kamala
>
>-------------- Original message --------------
>From: “Rex K. Perkins”
>
> > Hi folks,
> >
> > Is there any way to display the XMM registers in kernel mode in
> WinDBG? While
> > I’ve managed to get the registers displayed but they do not
> contain the correct
> > values.
> >
> > Also, is there any way to change the formatting? They appear
> stuck in the 32bit
> > float format.
> >
> > Thanks.
> >
> > -Rex.
What OS are you debugging? The kernel has many special rules about when
extended context state is captured/saved/restored. You may not be able
to get the info you want when you want it.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rex K. Perkins
Sent: Monday, February 13, 2006 8:05 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] XMM registers in WinDBG?
Thanks Kamala and Drew.
I was hoping to change the formatting of the GUI, but doing it from the
command line is fine.
Armed with these commands I can now dump random values in the format of
my choice. Alas even the r command does not display the content of the
register in kernel mode. For example:
1: kd> df ebx+30 L4
e3b9e070 0 0.5 2
8
1: kd> r xmm4:f
xmm4=5.60519e-045 0 8.33893e-010 -1.34533
1: kd> p
e31cfeee 0f286330 movaps xmm4,oword ptr [ebx+0x30]
1: kd> p
…
1: kd> r xmm4:f
xmm4=5.60519e-045 0 8.33893e-010 -1.34533
The value of xmm4 clearly changed over that instruction (to the values
shown in df) but WinDBG didn’t see that.
Is there any solution to this?
Thanks.
-Rex.
Subject: RE: XMM registers in WinDBG?
From: “Drew Bliss”
>Date: Fri, 10 Feb 2006 10:03:22 -0800
>X-Message-Number: 5
>
>Explicit r xmm#:type is the only way to display XMM registers in a
>non-default format. There is no way to set a general default, nor is
>there a way to influence the display of the registers in windbg’s
>registers window.
>
>We have these kinds of things on our list for future consideration, but
>they are low priority.
>
> ________________________________
>
>From: xxxxx@lists.osr.com on behalf of
>xxxxx@comcast.net
>Sent: Fri 2/10/2006 7:18 AM
>To: Kernel Debugging Interest List
>Subject: Re: [windbg] XMM registers in WinDBG?
>
>
>
>I was able to display in the format of my preference using the below
command:
>
>r xmm#:type, xmm#:type e.g., r xmm0:uq, xmm1:iq will display xmm0 in
>unsigned quad and xmm1 in signed quad
>
>However, I wasn’t able to set the format of my preference as default.
>BTW, WinDbg documentation has a list of types to choose from.
>
>Kamala
>
>-------------- Original message --------------
>From: “Rex K. Perkins”
>
> > Hi folks,
> >
> > Is there any way to display the XMM registers in kernel mode in
> WinDBG? While
> > I’ve managed to get the registers displayed but they do not
> contain the correct
> > values.
> >
> > Also, is there any way to change the formatting? They appear
> stuck in the 32bit
> > float format.
> >
> > Thanks.
> >
> > -Rex.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
This is from XP, 32 bit, though last time I tried it also failed on 64 bit.
The code in question is called from a display driver and plays by the
rules of XMM and MMX usage in the kernel. If this isn’t enough for
WinDBG, is there anything I could add to the driver to enable WinDBG
to see a full complement of CPU registers?
Thanks.
-Rex.
From: “Drew Bliss”
>Date: Mon, 13 Feb 2006 10:37:18 -0800
>X-Message-Number: 4
>
>What OS are you debugging? The kernel has many special rules about when
>extended context state is captured/saved/restored. You may not be able
>to get the info you want when you want it.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Rex K. Perkins
>Sent: Monday, February 13, 2006 8:05 AM
>To: Kernel Debugging Interest List
>Subject: Re:[windbg] XMM registers in WinDBG?
>
>Thanks Kamala and Drew.
>
>I was hoping to change the formatting of the GUI, but doing it from the
>command line is fine.
>
>Armed with these commands I can now dump random values in the format of
>my choice. Alas even the r command does not display the content of the
>register in kernel mode. For example:
>
>1: kd> df ebx+30 L4
>e3b9e070 0 0.5 2
>8
>1: kd> r xmm4:f
>xmm4=5.60519e-045 0 8.33893e-010 -1.34533
>1: kd> p
>e31cfeee 0f286330 movaps xmm4,oword ptr [ebx+0x30]
>1: kd> p
>…
>1: kd> r xmm4:f
>xmm4=5.60519e-045 0 8.33893e-010 -1.34533
>
>The value of xmm4 clearly changed over that instruction (to the values
>shown in df) but WinDBG didn’t see that.
>
>Is there any solution to this?
>
>Thanks.
>
>-Rex.
I’ll pass this no to the kernel team to get their feedback.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rex K. Perkins
Sent: Tuesday, February 14, 2006 6:50 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] XMM registers in WinDBG?
This is from XP, 32 bit, though last time I tried it also failed on 64
bit.
The code in question is called from a display driver and plays by the
rules of XMM and MMX usage in the kernel. If this isn’t enough for
WinDBG, is there anything I could add to the driver to enable WinDBG to
see a full complement of CPU registers?
Thanks.
-Rex.
From: “Drew Bliss”
>Date: Mon, 13 Feb 2006 10:37:18 -0800
>X-Message-Number: 4
>
>What OS are you debugging? The kernel has many special rules about
>when extended context state is captured/saved/restored. You may not be
>able to get the info you want when you want it.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Rex K. Perkins
>Sent: Monday, February 13, 2006 8:05 AM
>To: Kernel Debugging Interest List
>Subject: Re:[windbg] XMM registers in WinDBG?
>
>Thanks Kamala and Drew.
>
>I was hoping to change the formatting of the GUI, but doing it from the
>command line is fine.
>
>Armed with these commands I can now dump random values in the format of
>my choice. Alas even the r command does not display the content of the
>register in kernel mode. For example:
>
>1: kd> df ebx+30 L4
>e3b9e070 0 0.5 2
>8
>1: kd> r xmm4:f
>xmm4=5.60519e-045 0 8.33893e-010 -1.34533
>1: kd> p
>e31cfeee 0f286330 movaps xmm4,oword ptr [ebx+0x30]
>1: kd> p
>…
>1: kd> r xmm4:f
>xmm4=5.60519e-045 0 8.33893e-010 -1.34533
>
>The value of xmm4 clearly changed over that instruction (to the values
>shown in df) but WinDBG didn’t see that.
>
>Is there any solution to this?
>
>Thanks.
>
>-Rex.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com