public inbox for
 help / color / mirror / Atom feed
From: Andrew Cagney <>
To: Phil Muldoon <>
Cc: Frysk Hackers <>
Subject: Re: fhpd user interaction (and corefiles)
Date: Fri, 02 Nov 2007 13:50:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Phil Muldoon wrote:
> The question here then: if the LinuxHost code has a question for the 
> user, how does it ask that user the question via CoreCommand? As far 
> as I can tell, none of the fhpd commands are interactive.
As you point out, the bottom line is fstack, where no interaction 
is possible.  The create either succeeds or fails.  With that in mind 
can i suggest considering instead how you might interact with this from 
a UI.  For instance, would this work:
       use file browser to open a core file
    <<Core file assistant appears; perhaps pre-populated with info from 
raw core file>>
       - indicates what action is going to happen next, for instance 
indicates the executable it will attempt to open (or don't bother)
       - OK attempts to open the executable or fails leaving the user 
with the assistant
from a cli, a similar interaction might be:
   (fhpd) core foo
   Executable <exe> for <foo> not found.
   (fhpd) core foo exe                 --- the user is right
   (fhpd) core foo -noexe
another might be:
   (fhpd) core foo
   Corefile .... of arch ... no executable.      --- printed by fhpd 
using stuff from core
   (fhpd) exe ..the-exe...
   Corefile ... of arch ... executable ...      --- intercede the no-exe 
Each of these are built round the assumption that the code creating the 
core file is more predicatable (and more likely to throw an exception) 
for instance, interfaces with requirements such as:
   -- create core and must use implicit exe or fail
   -- create core and ignore exe
   -- create core and use explicit EXE


  reply	other threads:[~2007-11-02 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 10:03 Phil Muldoon
2007-11-02 13:50 ` Andrew Cagney [this message]
2007-11-05  9:52   ` Phil Muldoon
2007-11-08 11:25     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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