This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC-v5] Add windows OS Thread Information Block
- From: Pedro Alves <pedro at codesourcery dot com>
- To: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 1 Apr 2010 14:21:16 +0100
- Subject: Re: [RFC-v5] Add windows OS Thread Information Block
- References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> <201004011221.36972.pedro@codesourcery.com> <001801cad19a$cbcc40d0$6364c270$@muller@ics-cnrs.unistra.fr>
On Thursday 01 April 2010 13:56:50, Pierre Muller wrote:
> > Does the new packet return the TIB, or the TLB?
> The thread local base is the address of
> the Thread Information Block which itself
> is a block of memory (usually of size 0x1000)
> containing thread specific information.
Okay, thanks, that makes the terminology clearer.
> > The object is $_tlb now, isn't it?
> This object is a pointer in debuggee memory
> to the Thread Information Block.
If the TLB is a pointer to the TIB, then if "ptype $_tlb" shows
something not a pointer, something isn't right, wouldn't
you say? Isn't "ptype $_tlb"/"p $_tib" printing the _TIB_
instead? This is where things are still confusing.
> +@item $_tlb
> +@vindex $_tlb@r{, convenience variable}
> +The variable @code{$_tlb} is automatically set for Windows OS running
> +applications in native mode or connected to a gdbserver that supports
> +@code{qGetTIBAddr} requests. This variable contains the address of the
> thread
> +information block.
Does the variable really contain an address?
--
Pedro Alves