AMD Processors
Decrease font size
Increase font size
Topic Title: Windows API bug in Windows XP 64 for amd
Topic Summary:
Created On: 01/25/2004 10:17 AM
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 01/25/2004 10:17 AM
User is offline View Users Profile Print this message

Author Icon
jnavia
Junior Member

Posts: 7
Joined: 01/25/2004

There is a serious bug in the free (not checked) build of windows XP 64 bits.
The API
GetThreadContext
will deliver a context where all the floating point data will be zero!

I checked that I was including the CONTEXT_FLOATING_POINT flag when I ask for the context, and it is correctly set.

This bug can be seen in the WinDbg debugger for this system.
That debugger will never show any of the floating point registers
(st0-st7) in its register window.

This bug is serious since when the debugger wants to continue, it will set
the floating point state from the received state from windows.
Since the received state is all zeroes in the floating point part, this
means that the debugger will destroy all the floating point context
when it releases the program under debug.

Anybody knows about this bug and can confirm/infirm this?
Anybody knows about a work-around?

I am writing a compiler system for this CPU and I discovered this when
porting my debugger.

jacob navia
lcc-win32: a free compiler for windows
http://www.cs.virginia.edu:/~lcc-win32' ">http://www.cs.virginia.edu:/~lcc-win32
email: jacob@jacob.remcomp.fr
 01/25/2004 05:27 PM
User is offline View Users Profile Print this message

Author Icon
awd4dad
Member

Posts: 117
Joined: 10/06/2003

there should be a mail list at MSDN for this kind of problem.
Statistics
112018 users are registered to the AMD Processors forum.
There are currently 0 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2014 FuseTalk Inc. All rights reserved.



Contact AMD Terms and Conditions ©2007 Advanced Micro Devices, Inc. Privacy Trademark information