From: Mike Cvet <mcvet@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: Multi-Task Procs in the SourceWindow
Date: Mon, 16 Oct 2006 13:43:00 -0000 [thread overview]
Message-ID: <1161006197.2057.3.camel@towel.toronto.redhat.com> (raw)
In-Reply-To: <1160999501.3166.73.camel@dijkstra.wildebeest.org>
On Mon, 2006-10-16 at 13:51 +0200, Mark Wielaard wrote:
> Finally played with this. Very cool!
>
Thanks!
> The TreeView for the stacks is nice and compact. But I was wondering how
> to present stepping in this view (the InstructionObserver should give
> you the basics for the asm-step operation). Do we need a step-one-thread
> vs step-all-threads button? Or would that just add to the confusion?
Nope, that's exactly right - I'm trying to figure out the best way to
handle independent step-process and step-thread interfaces. In addition
to the run-process functionality the source window has I'll also need to
make a run-thread interface.
- Mike
prev parent reply other threads:[~2006-10-16 13:43 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
2006-10-16 13:45 ` Mike Cvet
2006-10-16 11:52 ` Mark Wielaard
2006-10-16 13:43 ` Mike Cvet [this message]
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=1161006197.2057.3.camel@towel.toronto.redhat.com \
--to=mcvet@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.org \
/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).