From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-17126-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 2624 invoked by alias); 26 Jul 2002 02:28:12 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 2609 invoked from network); 26 Jul 2002 02:28:10 -0000
Received: from unknown (HELO mta7.pltn13.pbi.net) (64.164.98.8)
  by sources.redhat.com with SMTP; 26 Jul 2002 02:28:10 -0000
Received: from modrick ([66.120.11.181])
 by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GZU0073G46XAX@mta7.pltn13.pbi.net> for
 gdb-patches@sources.redhat.com; Thu, 25 Jul 2002 19:28:10 -0700 (PDT)
Date: Thu, 25 Jul 2002 20:11:00 -0000
From: Mo DeJong <supermo@bayarea.net>
Subject: Re: [Patch] add implementation of stack-info-frame MI command
In-reply-to: <Pine.GSO.4.33.0207251700560.4104-100000@makita.cygnus.com>
To: gdb-patches@sources.redhat.com
Cc: ac131313@ges.redhat.com
Message-id: <20020725192807.0599e403.supermo@bayarea.net>
Organization: House of Mirth
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
References: <3D408BD9.90403@ges.redhat.com>
 <Pine.GSO.4.33.0207251700560.4104-100000@makita.cygnus.com>
X-SW-Source: 2002-07/txt/msg00529.txt.bz2

On Thu, 25 Jul 2002 17:03:57 -0700 (PDT)
Keith Seitz <keiths@redhat.com> wrote:

> On Thu, 25 Jul 2002, Andrew Cagney wrote:
> 
> > See my post to GDB.  I think this should be handled as an event and not
> > as a command.
> 
> As Mo has implemented, -stack-info-frame would return the very same
> information as -stack-info-depth.

It would? I was under the impression that -stack-info-depth would return
the number of frames on the stack without taking what the current frame
is into account.

-stack-info-depth
^done,depth="3"
(gdb) 
^done depth 3

-stack-info-frame
^done,level="0"
(gdb) 
^done level 0

up
^done,frame={level="1 ",addr="0x080484a8",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff5c4"}],file="resources.c",line="38"},line="38",file="resources.c"

-stack-info-depth
^done,depth="3"
(gdb) 

-stack-info-frame
^done,level="1"
(gdb) 


> I always thought that -stack-info-frame
> would give information about the current (or given) frame, i.e., saved pc,
> saved registers, etc.

I can't speak as to the original design goals. The existing documentation
for the command is not very clear about what it should do. I just
thought -stack-info-frame would work like -stack-select-frame in
that it would deal with an integer stack level. How is one meant to
query the stack level?

Mo