Re: [RFC] 32-bit support for windows thread information block

[Kai Tietz <Kai dot Tietz at onevision dot com>]

gdb-patches-owner@sourceware.org wrote on 14.01.2009 12:21:53:

>  I implemented two new command that display
> a part of the information of the
> thread information block and on
> the structured exception handler chain.
>  I added these two command to the "info w32" command
> prefix, but got into troubles appearing below.
> 
> I have several questions regarding the 64-bit support of
> windows nat files: 
> 
> 1) Do hardware watchpoints work?
>   the problem is that the dr[8] array is
> defined as a unsigned type,
> is this enough for win64?
>   Is "unsigned" type a 64-bit ?
> 
>   In the _CONTEXT struct 
>   the debug registers are defined as DWORD64...

For address above 4GB hardware watchpoints aren't working, reasoned by 
truncation.

> 2) Is GetThreadSelectorEntry function
> working in win64 ?
>   The reason of the question is that
> I have no win64 machine... so that I cannot test directly,
> the windows SDK says that it only works on i386 based
> machines, but that is sort of vague.
> Furthermore, the base address that is computed
> with this function is a 32bit address, so I am 
> wondering if it is meaningful or not...
Yes, it is present, but I am not sure if structure has still the same 
layout.

> The reason of the second question is that I have a
> patch that is able to display the thread information block
> and the structured exception handler chain on
> a win32 program, but I did not find much information on
> the the win64 equivalent, apart from the fact
> that it is apparently the $gs selector that is 
> used on x86_64 in windows64, instead of the $fs for win32.


Cheers,
Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.