public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: frysk-cvs@sourceware.org
Subject: frysk-core/frysk bindir/ChangeLog bindir/fstep ...
Date: Mon, 09 Jul 2007 16:31:00 -0000 [thread overview]
Message-ID: <20070709163130.19740.qmail@sourceware.org> (raw)
CVSROOT: /cvs/frysk
Module name: frysk-core
Changes by: mark@sourceware.org 2007-07-09 16:31:30
Modified files:
frysk/bindir : ChangeLog fstep.java
frysk/proc/live: ChangeLog LinuxTaskState.java
Added files:
frysk/bindir : TestFStep.java
Log message:
frysk-core/frysk/bindir/ChangeLog
2007-07-09 Mark Wielaard <mwielaard@redhat.com>
Fixes bug #4668
* fstep.java: Implement TaskObserver.Code.
(updateAttached): Depending on whether or not the user supplied a
command line to execute or a pid to trace either put a breakpoint
on the first real instruction or start tracing immediately. Return
Action.BLOCK.
(updateHit): New method.
(addedTo): Unblock task.
* TestFStep.java: New test.
frysk-core/frysk/proc/live/ChangeLog
2007-07-09 Mark Wielaard <mwielaard@redhat.com>
* LinuxTaskState.java (wantToAttachContinue): Add
handleAddObservation() and handleUnblock().
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/bindir/TestFStep.java.diff?cvsroot=frysk&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/bindir/ChangeLog.diff?cvsroot=frysk&r1=1.107&r2=1.108
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/bindir/fstep.java.diff?cvsroot=frysk&r1=1.9&r2=1.10
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/proc/live/ChangeLog.diff?cvsroot=frysk&r1=1.3&r2=1.4
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/proc/live/LinuxTaskState.java.diff?cvsroot=frysk&r1=1.2&r2=1.3
next reply other threads:[~2007-07-09 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 16:31 mark [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-17 17:12 cagney
2007-04-16 19:32 cagney
2007-01-23 16:24 cagney
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=20070709163130.19740.qmail@sourceware.org \
--to=mark@sourceware.org \
--cc=frysk-cvs@sourceware.org \
--cc=frysk@sourceware.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).