From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5398 invoked by alias); 26 Jun 2009 15:53:10 -0000 Received: (qmail 5364 invoked by uid 22791); 26 Jun 2009 15:53:07 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Jun 2009 15:52:58 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 03FF11062D; Fri, 26 Jun 2009 15:52:56 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id DA526105BB; Fri, 26 Jun 2009 15:52:55 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MKDjS-00044W-5m; Fri, 26 Jun 2009 11:52:54 -0400 Date: Fri, 26 Jun 2009 15:53:00 -0000 From: Daniel Jacobowitz To: Pierre Muller Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Add windows Thread Information Block Message-ID: <20090626155254.GA15627@caradoc.them.org> Mail-Followup-To: Pierre Muller , gdb-patches@sourceware.org References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00717.txt.bz2 On Fri, Jun 26, 2009 at 01:47:31AM +0200, Pierre Muller wrote: > - Current limits of stack > The last could be particularly interesting when we try to > to figure out an optimized stack frame. > > When we hit a frameless function without debug information, > we could try to find up the stack a valid pair of stored (EBP,EIP) > of the outer frame having a frame pointer. > Testing for EBP to bee within the limits given by > current_top_of_stack andcurrent_bottom_of_stack > would help to find correct pairs. Does Windows allow separate stacks, a la sigaltstack? Or is the stack always guaranteed to be within this range? > 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? You'd probably want a new 'target object' for this, and a qXfer packet to read it. Take a look at "info auxv", which is very similar. You might also want to consider treating this like $_siginfo. It's fine to also have an info command to display it, but I bet folks'll want to examine memory at some of these addresses or write scripts using them, so having it as a normal "struct value" would help. _siginfo is implemented using a target object, too. -- Daniel Jacobowitz CodeSourcery