From: Chris Moller <cmoller@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: ongoing frysk.proc.ptrace refactoring
Date: Tue, 22 May 2007 14:45:00 -0000 [thread overview]
Message-ID: <46530068.2090807@redhat.com> (raw)
In-Reply-To: <4652FE1B.8000004@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Andrew,
I'd planned to add MemorySpaceByteBuffer.java and commit a few changes
to TestByteBuffer.java in frysk-core/frysk/proc/ptrace later today--is
that going to mung up the stuff you're doing?
Chris
Andrew Cagney wrote:
> Just a work-in-progress update:
>
> While I've finished restructuring the target specific frysk.proc code
> into separate frysk.proc.corefile, frysk.proc.dummy and
> frysk.proc.ptrace packages there's still a ways to go as the
> refactoring has helped clarify several additional problems with the
> current code:
>
> -> frysk.proc.Proc and frysk.proc.Task seem to have gained a number of
> fields, such as Task.sig_send, that are very Linux/ptrace centric;
> the'll need to be cleaned up
>
> -> many of the methods, such as frysk.proc.Task.sendContinue, being
> ptrace specific (they do not apply to a corefile proc), can be moved
> to more specific packages
>
> -> rather than split along the lines of "corefile" and "ptrace", a
> better split might be "dead" (you can query a dead proc) and "live"
> (or stateful) (you can observe a live proc), re-consider that once the
> more pressing issues are addressed
>
> I'll be continuing with this.
>
> Andrew
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2007-05-22 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 14:38 Andrew Cagney
2007-05-22 14:45 ` Chris Moller [this message]
2007-05-22 15:10 ` Andrew Cagney
2007-05-22 16:32 ` Chris Moller
2007-05-22 17:08 ` Andrew Cagney
2007-05-22 22:44 ` Phil Muldoon
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=46530068.2090807@redhat.com \
--to=cmoller@redhat.com \
--cc=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).