public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
* local vs remote; core vs exe vs ...
@ 2008-01-08 18:55 Andrew Cagney
  2008-01-08 21:04 ` Phil Muldoon
  0 siblings, 1 reply; 2+ messages in thread
From: Andrew Cagney @ 2008-01-08 18:55 UTC (permalink / raw)
  To: frysk

Hi,

Lets consider one possible way that the user may be allowed to interact 
with local/remote machines:

   (fhpd) load /bin/bash
   [0] /bin/bash
   (fhpd) load remotemachine:/bin/bash
   [1] remotemachine:/bin/bash
   (fhpd) [0] start
   [0] running /bin/bash
   (fhpd) [1] start
   [1] running /bin/bash on remotemachine
   (fhpd)

and:

    (fhpd) core remotemachine:/a/core/file
    [0] remotemachine:/a/corefile
    (fhpd) print i
    (fhpd) start
    [0] running /corefile/exe on remotemachine

and to specify a sysroot:

    (fhpd) load remote:/bin/bash -sysroot /local/ia32
    (fhpd) load /bin/bash -sysroot remote:/ia32

As always the questions are:

Does this look reasonable?  ...?

What are the consequences?

1.

At present frysk has a Host specialized for each possible type of Proc: 
core, exe, ptrace, utrace.  If a CoreProc needs to be created, the 
LinuxCoreHost is used; similarly, if a new process needs to be started 
then the LinuxPtraceHost is used.  The above interaction, however, 
suggests to me that perhaps the Host should be factored differently vis:

        Host
          - requestCreateProc - start a new process
          - requestProc - find a running process
          - requestCoreProc - create a Proc from the core
          - requestExeProc - create a Proc from the exe
          |
          +---------------------------.
          |                           |
      LocalHost                   RemoteHost
        o requestCoreProc
        o requestExeProc
          |
          +---------------------.
  LocalLinuxPtraceHost   LocalLinuxUtraceHost
    o requestCreateProc    o requestCreateProc
    o requestProc          o requestProc

This lets us implement an operation such as "start" directly, for 
instance: Proc.Host.requestCreateProc(Proc.exe).

2.

When it comes to performing searches such as for shared libraries and 
executables, in addition to the local/remote host, there is a "search" 
object, the sysroot, that resolves lookups for debug information.

Andrew










^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: local vs remote; core vs exe vs ...
  2008-01-08 18:55 local vs remote; core vs exe vs Andrew Cagney
@ 2008-01-08 21:04 ` Phil Muldoon
  0 siblings, 0 replies; 2+ messages in thread
From: Phil Muldoon @ 2008-01-08 21:04 UTC (permalink / raw)
  To: Andrew Cagney; +Cc: frysk

Andrew Cagney wrote:
>
> Does this look reasonable?  ...?

Yes

>
> What are the consequences?

Immediately comes to mind are two things:

Wire protocol.
Transfer protocols: ssh? telnet? what does remotemachine: donate? AURL/I 
or some type?

Still thinking on the Host creation in the rest of the email.

Regards

Phil

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-01-08 21:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-08 18:55 local vs remote; core vs exe vs Andrew Cagney
2008-01-08 21:04 ` Phil Muldoon

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).