From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22189 invoked by alias); 26 Jun 2009 07:04:03 -0000 Received: (qmail 22139 invoked by uid 22791); 26 Jun 2009 07:04:02 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout6.012.net.il (HELO mtaout6.012.net.il) (84.95.2.16) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Jun 2009 07:03:45 +0000 Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KLU007003DTZ700@i-mtaout6.012.net.il> for gdb-patches@sourceware.org; Fri, 26 Jun 2009 10:03:42 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.213.34]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KLU00E7N3M56P60@i-mtaout6.012.net.il>; Fri, 26 Jun 2009 10:03:42 +0300 (IDT) Date: Fri, 26 Jun 2009 07:04:00 -0000 From: Eli Zaretskii Subject: Re: [RFC] Add windows Thread Information Block In-reply-to: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> To: Pierre Muller Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83r5x7zdbm.fsf@gnu.org> References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00705.txt.bz2 > From: "Pierre Muller" > Date: Fri, 26 Jun 2009 01:47:31 +0200 > > The current patch adds the code to windows-nat.c > despite the fact that I added the thread_local_base field > to both windows-nat.c and gdbserver/win32-low.c. > To be also usable for a remote gdbserver, > I would need to move that to windows-tdep.c > > But here I need advice on how to move the display_tib function > to windows-tdep.c file, as it is currently using internal information > of windows-nat.c thread_info struct. > Also how should I handle the remote case? > Should I add a new query, something like 'qTlb'? > How should I call this from windows-tdep code? > > All comments welcomed! If this patch is accepted, we will need a corresponding patch for the manual, describing the new command "tib". (Btw, how about a more descriptive name?) Thanks.