From: Keith Seitz <keiths@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Mo DeJong <supermo@bayarea.net>, <gdb-patches@sources.redhat.com>
Subject: Re: [Patch] add implementation of stack-info-frame MI command
Date: Thu, 25 Jul 2002 17:05:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0207251700560.4104-100000@makita.cygnus.com> (raw)
In-Reply-To: <3D408BD9.90403@ges.redhat.com>
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. I always thought that -stack-info-frame
would give information about the current (or given) frame, i.e., saved pc,
saved registers, etc.
> The user entering a command like ``up'' needs to trigger the event
> notification anyway.
As for "up"/"down"/"frame" commands to the console, I have already
implemented a notification event on the "mi branch".
Keith
next prev parent reply other threads:[~2002-07-26 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 15:10 Mo DeJong
2002-07-25 17:04 ` Andrew Cagney
2002-07-25 17:05 ` Keith Seitz [this message]
2002-07-25 20:11 ` Mo DeJong
2002-07-25 22:33 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.33.0207251700560.4104-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=supermo@bayarea.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox