From: Mark Wielaard <mark@klomp.org>
To: Mike Cvet <mcvet@redhat.com>
Cc: Yao Qi <qiyaoltc@cn.ibm.com>, frysk@sourceware.org
Subject: Re: Multi-Task Procs in the SourceWindow
Date: Mon, 16 Oct 2006 11:59:00 -0000 [thread overview]
Message-ID: <1160999930.3166.76.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1160511976.2082.8.camel@towel.toronto.redhat.com>
On Tue, 2006-10-10 at 16:26 -0400, Mike Cvet wrote:
> On Tue, 2006-10-10 at 09:46 +0800, Yao Qi wrote:
> > 2) When I click one frame, there are multiple lines are highlighted.
> > For example, If I click "baz" in StackWindow, line #42, #50, and #57
> > are highlighted at the same time. Is it expected? IMO, we could only
> > highlight the *current* frame, instead of call tree, which has been
> > displayed in StackWindow.
>
> Yeah, I was wondering about this one myself. I *could* see usefulness
> for this, but more often than not its probably confusing. I'll get rid
> of it for now
It would be cool to show arrows to visualize the whole call stack in the
current source file. But that is probably not trivial to implement. But
maybe highlight the current selected frame brightly, and highlight the
other frames in the call stack dimmed out/grayed?
Cheers,
Mark
next prev parent reply other threads:[~2006-10-16 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 16:15 Mike Cvet
2006-10-10 1:47 ` Yao Qi
2006-10-10 19:13 ` Andrew Cagney
2006-10-10 19:46 ` Rick Moseley
2006-10-10 20:26 ` Mike Cvet
2006-10-16 11:59 ` Mark Wielaard [this message]
2006-10-16 13:45 ` Mike Cvet
2006-10-16 11:52 ` Mark Wielaard
2006-10-16 13:43 ` Mike Cvet
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=1160999930.3166.76.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=mcvet@redhat.com \
--cc=qiyaoltc@cn.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).