From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27595] New: dwz -o outfile with implicit file argument
Date: Wed, 17 Mar 2021 13:26:13 +0000 [thread overview]
Message-ID: <bug-27595-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27595
Bug ID: 27595
Summary: dwz -o outfile with implicit file argument
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
Consider this session:
...
$ rm -f a.out b.out
$ gcc ~/hello.c -g
$ ls a.out
a.out
$ dwz -o b.out
$ ls b.out
b.out
$
...
The advertised usage looks like this:
...
$ ./dwz -?
Usage:
./dwz [common options] [-h] [-m COMMONFILE] [-M NAME | -r] [FILES]
./dwz [common options] -o OUTFILE FILE
./dwz [ -v | -? ]
...
But the actual dwz use we did above suggests instead:
...
./dwz [common options] -o OUTFILE [ FILE ]
...
So, we should either update the advertised usage, or require an explicit file
when using -o.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-17 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 13:26 vries at gcc dot gnu.org [this message]
2021-03-22 5:43 ` [Bug default/27595] " vries at gcc dot gnu.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=bug-27595-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).