public inbox for
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <>
Subject: [Bug tools/29786] Unable to understand, in objdump, the user is not using the name, so using a.out
Date: Tue, 15 Nov 2022 20:55:54 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
         Resolution|---                         |NOTABUG
                 CC|                            |fche at redhat dot com
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Why not use an empty string as a filename?  A user can type

     eu-objdump ""

to pass an empty string if that's really what she wants.
Defaulting to "a.out" in the absence of a filename is traditional.

You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2022-11-15 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:52 [Bug tools/29786] New: " zhuorong.lin at outlook dot com
2022-11-15 20:55 ` fche at redhat dot com [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:

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