From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: "Jim Blandy" <jimb@codesourcery.com>,
"Frederic RISS" <frederic.riss@st.com>,
"Frédéric Riss" <frederic.riss@gmail.com>,
"Vladimir Prus" <ghost@cs.msu.su>,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] Prints the frame id when target stops
Date: Sat, 20 Jan 2007 17:00:00 -0000 [thread overview]
Message-ID: <20070120170000.GA17591@nevyn.them.org> (raw)
In-Reply-To: <45B0D560.1050906@st.com>
On Fri, Jan 19, 2007 at 03:27:44PM +0100, Denis PILAT wrote:
> As there is no consensus to modify the -stack-list-frames to perform
> cache in a safe way, putting the frame_id (like discussed before) in the
> MI output allows the front end to make a compromise that isn't possible
> in GDB, and for some cases, the front end will be able to not get the
> stack list frame at all.
I understand that front end authors may want to make compromises that
we, the GDB developers, don't (in order to improve performance).
However, I don't want to provide an interface that looks simple
but carries these kinds of pitfalls if I can avoid it.
Maybe you can use Nick's MI timings patch, or a system profiler like
oprofile / vtune, to get some better idea of where time is being spent.
If we can make things fast enough, we should.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-20 17:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 16:21 Denis PILAT
2007-01-15 21:37 ` Nick Roberts
2007-01-15 23:11 ` Nick Roberts
2007-01-15 23:49 ` Nick Roberts
2007-01-17 8:26 ` Denis PILAT
2007-01-16 16:20 ` Vladimir Prus
2007-01-16 21:12 ` Nick Roberts
2007-01-16 23:38 ` Vladimir Prus
2007-01-17 6:18 ` Daniel Jacobowitz
2007-01-17 21:46 ` Vladimir Prus
2007-01-20 17:02 ` Daniel Jacobowitz
2007-01-17 21:29 ` Mark Kettenis
2007-01-17 21:38 ` Vladimir Prus
2007-01-17 21:59 ` Frédéric Riss
2007-01-17 22:14 ` Vladimir Prus
2007-01-18 8:00 ` Frederic RISS
2007-01-17 22:17 ` Daniel Jacobowitz
2007-01-18 7:58 ` Frederic RISS
2007-01-18 18:34 ` Jim Blandy
2007-01-19 14:28 ` Denis PILAT
2007-01-20 17:00 ` Daniel Jacobowitz [this message]
2007-01-18 19:59 ` Daniel Jacobowitz
2007-01-17 6:19 ` Daniel Jacobowitz
2007-01-18 21:13 ` Nick Roberts
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=20070120170000.GA17591@nevyn.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=frederic.riss@gmail.com \
--cc=frederic.riss@st.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=jimb@codesourcery.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