From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: moving frysk.proc.LinuxPtrace* to frysk.proc.ptrace.Linux*
Date: Mon, 14 May 2007 16:51:00 -0000 [thread overview]
Message-ID: <4648928D.4000607@redhat.com> (raw)
Just an update and heads up to the on-going task of breaking-out the
os-specific code in frysk.proc, moving it to more specialized packages vis:
frysk.proc.dummy - a dummy host - "done"
frysk.proc.corefile - a host built from core-files - "done"
frysk.proc.ptrace - a host built using ptrace(2) calls
For frysk.proc.ptrace, there'll likely soon be some interesting fallout:
-> as WIP have << frysk.proc.ptrace.LinuxHost extend
frysk.proc.LinuxPtraceHost extend frysk.proc.Host >>, (perhaps also
similar for Task and Proc?) so that code can more incrementally be
switched to the new frysk.proc.ptrace package
-> Eliminate methods such as <<abstract void Task.sendAttach()>> from
frysk.proc.Task inlining the implementation into
frysk.proc.ptrace.LinuxTaskState; they assume "ptrace" semantics which
only applies to ptrace
-> Add more manipulation methods, such as proc.reparent(Proc) to
abstract some of the tree manipulation operations
take care,
Andrew
reply other threads:[~2007-05-14 16:47 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=4648928D.4000607@redhat.com \
--to=cagney@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).