From: Andrew Cagney <cagney@redhat.com>
To: Tim Moore <timoore@redhat.com>, Mike Cvet <mcvet@redhat.com>
Cc: frysk@sourceware.org
Subject: frysk.rt.SteppingEngine poking at a task's blocker list?
Date: Thu, 05 Jul 2007 21:05:00 -0000 [thread overview]
Message-ID: <468D5D0C.10505@redhat.com> (raw)
Tim, Mike,
I noticed this in frysk.rt.SteppingEngine:
/**
* Unblock a task so that, from the point of view of the stepping
* engine, execution can continue. For now this unblocks
* instruction observers and code observers for breakpoints, but
* ultimately I (timoore) think it should unblock all blockers.
*/
public boolean continueForStepping(Task task, boolean unblockStepper) {
if (unblockStepper) {
task.requestUnblock(this.steppingObserver);
}
TaskObserver[] blockers = (TaskObserver
[])task.getBlockers().clone();
for (int j = 0; j < blockers.length; j++) {
// One of ours?
if (blockers[j] instanceof Breakpoint) {
task.requestUnblock(blockers[j]);
} else {
// Some blocker that we don't know about
// System.out.println("Unknown blocker " +
blockers[j].toString());
// return false;
}
}
return true;
}
I'm not sure what is happening here, but the underlying code should
operate as:
-> process hits a breakpoint instruction
-> all low-level CodeObservers fire
-> all corresponding high-level Breakpoint observers fire
-> Breakpoint observers each notify Stepping engine to stop (accompanied
by corresponding low-level CodeObserver doing the block)
This will leave the SteppingEngine with a full list of CodeObservers to
unblock without needing to poke around an assumed live task's internal
state.
The flexibility of this approach also lets us write custom high-level
breakpoint observers, in the monitor say, that can be implemented using
just the Breakpoint and its shared-library Manager, and not have to
worry about the stepping engine at all.
Andrew
PS: And it prevents me moving this blockers stuff into frysk.proc.live
:-( :-)
next reply other threads:[~2007-07-05 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 21:05 Andrew Cagney [this message]
2007-07-06 14:04 ` Tim Moore
2007-07-06 14:25 ` Mike Cvet
2007-07-06 19:38 ` Andrew 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=468D5D0C.10505@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=mcvet@redhat.com \
--cc=timoore@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).