From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27100 invoked by alias); 23 Jun 2007 19:08:46 -0000 Received: (qmail 27092 invoked by uid 22791); 23 Jun 2007 19:08:45 -0000 X-Spam-Check-By: sourceware.org Received: from shell4.bayarea.net (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 23 Jun 2007 19:08:43 +0000 Received: (qmail 17670 invoked from network); 23 Jun 2007 12:08:41 -0700 Received: from 209-128-106-254.bayarea.net (HELO ?192.168.20.7?) (209.128.106.254) by shell4.bayarea.net with SMTP; 23 Jun 2007 12:08:41 -0700 Message-ID: <467D6FB8.4080909@eagercon.com> Date: Sat, 23 Jun 2007 19:08:00 -0000 From: Michael Eager User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Stan Shebs CC: gdb@sources.redhat.com Subject: Re: What's an annex? stratum? References: <467D5FEF.7010900@eagercon.com> <467D6D1F.7090507@earthlink.net> In-Reply-To: <467D6D1F.7090507@earthlink.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00217.txt.bz2 Stan Shebs wrote: > Michael Eager wrote: >> Looking at target.c, I see some terms which are less >> than clear: annex and stratum. Could someone tell me >> what these mean? > "Annex" is apparently an introduction of Andrew's from 2004, does kind > of look like an address space addition, although not clear that it's > fully implemented. I'm assuming that the XML target description in the docs is similarly incomplete and/or obsolete. There seems to be a fair amount of cruft in the code, and even more in the documentation. Sigh. > "Stratum" is an old concept, merely a way to talk about different levels > of the target stack. In practice, the stacking concept isn't as clean as > it must have seemed initially; sometimes you really want to run a target > op in a vector down in the stack, sometimes you want to replace a target > vector in the middle. So we introduce strata as a way to find a > mid-stack target vector of a desired type. First big block comment in > target.h goes into a bit more detail. I read the comments, but it doesn't really say what the target stack is. I see the enum for different strata, giving a hierarchy. I can see that you might layer a core file on top of an executable file, so that searching for a symbol/address was passed down until you found the one which contained it. But how does thread/process/ download fit into this picture? -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077