From: Nick Roberts <nickrob@snap.net.nz>
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: RE: Changing "info frame" output?
Date: Wed, 03 Nov 2004 20:49:00 -0000 [thread overview]
Message-ID: <16777.17132.404232.210442@farnswood.snap.net.nz> (raw)
> and with that in mind have come up with the following as a draft:
> Stack level 1, frame at 0x7ffff240:
> Code at 0x1005e5f8 in fprintf_filtered (stream=0x10467888,
> format=0x10371b74 "GNU gdb %s\n")
> at /home/scratch/PENDING/2004-10-29-full-location/src/gdb/utils.c:2231
> called by frame at 0x7ffff260, caller of frame at 0x7ffff1c0
> Source language c.
> Frame base at 0x7ffff1c0.
> Registers saved by this frame:
> pc at 0x7ffff244, lr at 0x7ffff244
...
> thoughts,
Well gdb-ui.el in CVS Emacs uses the existing info frame" output to update the
GUI. If you are going to change this output then I think it is important to
have an equivalent MI command whose output is stable. I started a thread about
this on the gdb mailing list back in June, and posted a patch, probably lousy,
on gdb-patches:
http://sources.redhat.com/ml/gdb-patches/2004-06/msg00652.html
to describe the functionality I was hoping to have and which was titled:
[RFC] (was Re: How does GDB/MI give the current frame).
Could this be included in the discussion too, please.
Nick
Update on Emacs: We're six months into the feature freeze and there still
hasn't been a pretest. Emacs is starting to look like one of those immaculate
classic cars that goes everywhere on a trailer. Well you wouldn't want to
get it dirty, would you?
next reply other threads:[~2004-11-03 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 20:49 Nick Roberts [this message]
2004-11-05 15:00 ` Andrew Cagney
2004-11-05 19:53 ` How can GDB/MI give the current frame (was Re: Changing "info frame" output?) Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 7:28 Changing "info frame" output? Paul Schlie
2004-11-03 16:28 Andrew Cagney
2004-11-04 21:59 ` Mark Kettenis
2004-11-05 14:53 ` Andrew Cagney
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=16777.17132.404232.210442@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