This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC-v2] Add windows Thread Information Block

From: Christopher Faylor <cgf-use-the-mailinglist-please at sourceware dot org>
To: 'Daniel Jacobowitz' <drow at false dot org>, gdb-patches at sourceware dot org, Pedro Alves <pedro at codesourcery dot com>, Pierre Muller <muller at ics dot u-strasbg dot fr>
Date: Wed, 1 Jul 2009 15:10:04 -0400
Subject: Re: [RFC-v2] Add windows Thread Information Block
References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> <001f01c9fa5a$0e1297f0$2a37c7d0$@u-strasbg.fr> <20090701181013.GA8215@ednor.casa.cgf.cx> <200907011921.15134.pedro@codesourcery.com>

On Wed, Jul 01, 2009 at 07:21:14PM +0100, Pedro Alves wrote:
>On Wednesday 01 July 2009 19:10:13, Christopher Faylor wrote:
>>Do we really have to reinvent this structure here?  ?Can't we use a
>>Windows header definition rather than inventing our own?
>>
>
>We can't.  We need it for cross gdb configurations too.  But I'm not
>sure the structure will still appear as is, if Pierre updates the patch
>to implement $_tid.

It's unreasonable to assume that a cross gdb configuration which
understands Windows would be able to use the w32api header files?

cgf

Follow-Ups:
- Re: [RFC-v2] Add windows Thread Information Block
  - From: Pedro Alves

References:
- [RFC-v2] Add windows Thread Information Block
  - From: Pierre Muller
- Re: [RFC-v2] Add windows Thread Information Block
  - From: Christopher Faylor
- Re: [RFC-v2] Add windows Thread Information Block
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]