From: Nick Roberts <nickrob@snap.net.nz>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: How can GDB/MI give the current frame (was Re: Changing "info frame" output?)
Date: Fri, 05 Nov 2004 19:53:00 -0000 [thread overview]
Message-ID: <16779.55504.399642.43004@farnswood.snap.net.nz> (raw)
In-Reply-To: <418B956D.7050800@gnu.org>
> What exactly does EMACS use? Sigh!
Very little. Just the address, procedure name, filename and line no. (if
available). I used the command "frame" initially, but its output wasn't as
consistent.
> Start a new thread (I don't know why I missed it). My only memory in
> this area is that there needs to be both a light-weight and heavy weight
> frame info call (info frame is heavy weight - it forces a full frame
> unwind).
It sounds like all I would need is the lightweight call via MI. I called `my
command' "-stack-info-frame", after looking at the GDB manual, and out of
ignorance. "-stack-frame" might be more appropriate.
Nick
prev parent reply other threads:[~2004-11-05 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 20:49 Changing "info frame" output? Nick Roberts
2004-11-05 15:00 ` Andrew Cagney
2004-11-05 19:53 ` Nick Roberts [this message]
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=16779.55504.399642.43004@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/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