From: Jason Molenda <jmolenda@apple.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -stack-select-frame
Date: Thu, 16 Jun 2005 23:30:00 -0000 [thread overview]
Message-ID: <412387CD-8F52-46E0-865F-560543C1E757@apple.com> (raw)
In-Reply-To: <17074.1440.40908.588287@farnswood.snap.net.nz>
On Jun 16, 2005, at 4:05 PM, Nick Roberts wrote:
> I thought it would save some time if the user doesn't need to see the
> whole stack.
FWIW we've done a lot of careful timing analysis, and the back &
forth communication between our GUI and gdb is so fast as to be
pointless to optimize. We original considered adding special purpose
"give Xcode everything it needs to know at a breakpoint hit" type
commands but when we saw how fast the majority of MI commands can
execute & be parsed by the GUI, it was obvious that this was not a
useful area to optimize. And frankly, in my anecdotal experience,
MacOS X isn't the fastest OS at things like "two processes talking
over a pipe".
(one of the parts of this profiling which is especially useful is
that we have a "mi-timings-enabled" setting. When it's enabled,
every MI command reports how long gdb took to complete it, e.g. the
"time=" bit at the end here:
-> 50-stack-list-frames 0 5
<- 50^done,stack=[frame=
{level="0",addr="0x0009e7fc",fp="0xbfffe700",func=" [...] ,frame=
{level="5",addr="0x936265d0",fp="0xbfffeee0",func="-[NSApplication
run]"}],time=
{wallclock="0.14353",user="0.00584",system="0.00335",start="1118952348.0
03847",end="1118952348.147372"}
we have similar timestamps put out by the GUI so when there's a
slowdown we can establish where time was being spent.)
>>> enum mi_cmd_result
>>> mi_cmd_stack_select_frame (char *command, char **argv, int argc)
>>> {
>>> - if (!target_has_stack)
>>> - error (_("mi_cmd_stack_select_frame: No stack."));
>>> -
>>>
>
> Because now GDB will report it as follows:
>
> -stack-select-frame
> &"No stack.\n"
> ^error,msg="No stack."
> (gdb)
You're right, currently it behaves like this:
-stack-select-frame
&"mi_cmd_stack_select_frame: No stack.\n"
^error,msg="mi_cmd_stack_select_frame: No stack."
(gdb)
but select_frame_command () will throw the error eventually, so
there's no need to do the additional check here.
J
next prev parent reply other threads:[~2005-06-16 23:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 3:36 Nick Roberts
2005-06-16 4:42 ` Daniel Jacobowitz
2005-06-16 6:41 ` Nick Roberts
2005-06-16 13:21 ` Daniel Jacobowitz
2005-06-16 22:58 ` Nick Roberts
2005-06-16 23:20 ` Bob Rossi
2005-06-16 23:47 ` Daniel Jacobowitz
2005-06-17 3:07 ` Nick Roberts
2005-06-17 3:21 ` Daniel Jacobowitz
2005-06-17 7:37 ` Nick Roberts
2005-06-17 10:15 ` Eli Zaretskii
2005-06-17 13:33 ` Daniel Jacobowitz
2005-06-18 8:56 ` Eli Zaretskii
2005-06-17 9:55 ` Eli Zaretskii
2005-06-17 9:46 ` Eli Zaretskii
2005-06-16 18:23 ` Eli Zaretskii
2005-06-16 20:15 ` Jason Molenda
2005-06-16 23:04 ` Nick Roberts
2005-06-16 23:30 ` Jason Molenda [this message]
2005-06-17 7:22 ` Nick Roberts
2005-06-17 13:30 ` Daniel Jacobowitz
2005-06-17 19:48 ` Jason Molenda
2005-06-17 22:35 ` Stan Shebs
2005-06-17 22:59 ` Daniel Jacobowitz
2005-06-17 23:31 ` Nick Roberts
[not found] <1119003319.5434.ezmlm@sources.redhat.com>
2005-06-17 17:45 ` Jim Ingham
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=412387CD-8F52-46E0-865F-560543C1E757@apple.com \
--to=jmolenda@apple.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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