From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: fhpd user interaction (and corefiles)
Date: Thu, 08 Nov 2007 11:25:00 -0000 [thread overview]
Message-ID: <4732F23E.8060504@redhat.com> (raw)
In-Reply-To: <472EE7E6.9050609@redhat.com>
Phil Muldoon wrote:
> Andrew Cagney wrote:
>> 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.
Further on from yesterdays talks, this is the workflow:
(fhpd) core core.1234
Error: Could not find executable: 'a.out' specified for corefile. You
can specify one with the core command. E.g: core core.file yourexefile.
Alternatively you can tell fhpd to ignore the executable with -noexe.
E.g core core.file -noexe. No corefile has been loaded at this time.
Then from that point:
core core.1234 -noexe
(basic metadata only)
or
core core.1234 /home/foo/a.out
(override exe option in the corefile)
There's an issue here. How do you lint that /home/foo/a.out really is
the executable that matches the corefiles? I could check the name in
the corefile, but that sort of negates the point of having an overriding
executable. If it is not the executable, the metadata builders gets very
confused pretty fast as the PT_LOADS in the exe look nothing like they
should.
This leads onto another question. If a set is "half built" as it were,
how does one clear that set and start from fresh? Or just simply replace
whatever is in that set, good or bad, with a new fresh set of processes
and tasks?
Regards
Phil
prev parent reply other threads:[~2007-11-08 11:25 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
2007-11-05 9:52 ` Phil Muldoon
2007-11-08 11:25 ` Phil Muldoon [this message]
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=4732F23E.8060504@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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).