public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5924] New: fhpd has no <EXEFILE> arguments help
Date: Thu, 13 Mar 2008 08:37:00 -0000	[thread overview]
Message-ID: <20080313083652.5924.jan.kratochvil@redhat.com> (raw)

fhpd --help does not document how to pass the <EXEFILE> arguments.

Current:
Usage: fhpd <PID> || fhpd <EXEFILE> || fhpd <COREFILE> [<EXEFILE>]
Expected:
Usage: fhpd <PID> || fhpd <EXEFILE> [<ARGUMENTS>] || fhpd <COREFILE> [<EXEFILE>]

Resulting in blind attempts to run it as:
fhpd gdb -ex 'print 1+1'
        fhpd: unrecognized option '-ex'

P.S.:
When changing the help I would expect either the syntax
usage: fhpd <pid> || fhpd <exefile> [<arguments>] || fhpd <corefile> [<exefile>]
or
Usage: fhpd PID || fhpd EXEFILE [ARGUMENTS] || fhpd COREFILE [EXEFILE]
to be more compliant with the standards in use.

frysk-0.0.1.2008.02.29.rh1-1.fc8.x86_64

-- 
           Summary: fhpd has no <EXEFILE> arguments help
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: jan dot kratochvil at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5924

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2008-03-13  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  8:37 jan dot kratochvil at redhat dot com [this message]
2008-03-13 14:49 ` [Bug general/5924] " cagney at redhat dot com
2008-10-21 21:44 ` cagney at sourceware dot org

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=20080313083652.5924.jan.kratochvil@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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).