From: Vladimir Prus <ghost@cs.msu.su>
To: Robert Dewar <dewar@adacore.com>
Cc: Jim Ingham <jingham@apple.com>, gdb@sources.redhat.com
Subject: Re: MI: performance of getting stack arguments
Date: Wed, 19 Apr 2006 07:30:00 -0000 [thread overview]
Message-ID: <200604191010.40548.ghost@cs.msu.su> (raw)
In-Reply-To: <44455B87.2020800@adacore.com>
On Wednesday 19 April 2006 01:35, Robert Dewar wrote:
> > Also, in a GUI much more stuff is visible at once, so if each element is
> > too complex then the overall result is noisy and hard to use. Visual
> > Studio used by default to show a whole bunch of junk in the stack window
> > (pc, args, etc.) and way back when I used it I found it really hard to
> > look at for just this reason. According to the 2005 Online docs, you
> > can turn all the other info off and display just the function name if
> > you want...
>
> Seems reasonable to have a much more streamlined call stack visible all
> the time, and a special command to decorate it with parameter values.
Good idea! I'll think about it.
Thanks,
Volodya
next prev parent reply other threads:[~2006-04-19 6:11 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 [this message]
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
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=200604191010.40548.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=dewar@adacore.com \
--cc=gdb@sources.redhat.com \
--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