From: Mike Cvet <mcvet@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: Continue/Stop in the SourceWindow
Date: Thu, 12 Oct 2006 20:42:00 -0000 [thread overview]
Message-ID: <1160685766.2082.40.camel@towel.toronto.redhat.com> (raw)
With regards to #3346, the SW will now continue and stop a process
entirely, re-generating the stack trace for all threads and DOM source
code displayed in the window.
This functionality is achieved through the run/stop buttons now
available in the toolbar.
As usual, I'm always looking for bugs - if you find any, please file
them to me, and hang them off of #3346 if you can.
Thanks!
- Mike
reply other threads:[~2006-10-12 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1160685766.2082.40.camel@towel.toronto.redhat.com \
--to=mcvet@redhat.com \
--cc=frysk@sources.redhat.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).