From: Eli Zaretskii <eliz@gnu.org>
To: Jim Ingham <jingham@apple.com>
Cc: dewar@adacore.com, ghost@cs.msu.su, gdb@sources.redhat.com
Subject: Re: MI: performance of getting stack arguments
Date: Wed, 19 Apr 2006 12:40:00 -0000 [thread overview]
Message-ID: <u64l6x8bt.fsf@gnu.org> (raw)
In-Reply-To: <EFF204DE-4C25-4F2A-A622-8605B2996BC9@apple.com> (message from Jim Ingham on Tue, 18 Apr 2006 14:17:24 -0700)
> Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> From: Jim Ingham <jingham@apple.com>
> Date: Tue, 18 Apr 2006 14:17:24 -0700
>
> But just keep in
> mind, when you are implementing a GUI debugger that anything you show
> in the UI you are pledging to update every time a step is completed.
> And most folks are pretty sensitive about how long it takes for each
> step to complete. So you do need to be a bit conservative about what
> you display by default. Adding to this, gdb does get slow as
> programs get large, which makes it even more important to be judicious.
How about if we implement a facility to send just the changes in the
call stack since the last time the stack was sent? This way, the
amount of stuff sent each stop will be much smaller, I think.
next prev parent reply other threads:[~2006-04-19 8:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 16:40 Vladimir Prus
2006-04-18 16:45 ` Daniel Jacobowitz
2006-04-18 21:15 ` Jim Ingham
2006-04-19 7:55 ` Vladimir Prus
2006-04-19 16:13 ` Eli Zaretskii
2006-04-20 8:50 ` Daniel Jacobowitz
2006-04-26 14:10 ` Vladimir Prus
2006-04-26 14:59 ` Daniel Jacobowitz
2006-04-26 18:02 ` Vladimir Prus
2006-04-26 18:17 ` Daniel Jacobowitz
2006-04-18 19:11 ` Jim Ingham
2006-04-18 21:35 ` Robert Dewar
2006-04-18 21:37 ` Jim Ingham
2006-04-19 6:08 ` Robert Dewar
2006-04-19 7:30 ` Vladimir Prus
2006-04-19 6:11 ` Nick Roberts
2006-04-19 8:45 ` Eli Zaretskii
2006-04-19 9:02 ` Nick Roberts
2006-04-19 12:40 ` Eli Zaretskii [this message]
2006-04-20 10:22 ` Jim Ingham
2006-04-19 6:20 ` Vladimir Prus
2006-04-19 8:28 ` Eli Zaretskii
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=u64l6x8bt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dewar@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=jingham@apple.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