From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: step-by-step
Date: Fri, 13 Oct 2006 14:17:00 -0000 [thread overview]
Message-ID: <452FA01B.2010500@redhat.com> (raw)
In-Reply-To: <1160694767.3111.38.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
> Hi,
>
> On Fri, 2006-10-13 at 00:12 +0200, Mark Wielaard wrote:
>
>> This adds a first pass at the stepping Instruction observer. There
>> aren't any new testcases yet (but a little demo program will follow
>> right after this email).
>>
>
> Here is a little toy fstep that uses it.
>
Mark,
fstep is more than a toy. Having been reduced to using an instruction
tracing simulator to track down an SMP races, this forms the foundation
of an extremely wicked tool!
I created http://sourceware.org/bugzilla/show_bug.cgi?id=3364
Andrew
next prev parent reply other threads:[~2006-10-13 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 22:12 step-by-step Mark Wielaard
2006-10-12 23:12 ` step-by-step Mark Wielaard
2006-10-13 14:17 ` Andrew Cagney [this message]
2006-10-18 1:01 ` step-by-step Yong Zheng
2006-10-18 1:28 ` step-by-step Roland McGrath
2006-10-18 14:26 ` step-by-step Andrew Cagney
2006-10-19 0:51 ` step-by-step Yong Zheng
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=452FA01B.2010500@redhat.com \
--to=cagney@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).