Re: MI: performance of getting stack arguments

Eli Zaretskii
2006-04-19T08:45:12Z

> 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.