From: "Nguyễn Gia Phong via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 72535@debbugs.gnu.org
Cc: julien@lepiller.eu, simon.tournier@u-paris.fr
Subject: bug#72535: bap is missing all subcommands
Date: Fri, 09 Aug 2024 17:20:45 +0900 [thread overview]
Message-ID: <D3B895OQFPEU.3LN72IL730XK5@guix> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Hello Guix,
I noticed that bap (binary analysis platform)'s executable
is missing all subcommands:
--8<---------------cut here---------------start------------->8---
$ guix shell bap
$ bap /bin/sh # default to disassemble
bap: unknown command 'disassemble', must be either '.' or 'list'.
Usage: bap [COMMAND] ?
Try 'bap --help' for more information.
$ bap
Usage:
bap <COMMAND> [<OPTIONS>]
Common options:
--version prints the version number and exits;
--plugin-path <DIR> adds <DIR> to the plugins search path;
--logdir <DIR> creates a log file in <DIR>;
--recipe <VAL> extracts command line arguments from the recipe.
Commands:
Plugins:
If no command line options or arguments are specified, then this
message is printed. To hush this message specify the `.' command,
e.g., `bap .'. The command could be omitted altogether, in that case the
`disassemble' command is assumed, e.g., `bap /bin/ls' is the same
as `bap disassemble /bin/ls'. Not that the default command is
subject to change, so it is better not to rely on this behavior in
your automation tools.
Run 'bap <COMMAND> --help' for more information a command.
Run 'bap --<PLUGIN>-help for more information about a plugin.
Run 'bap --help' for the detailed manual.
--8<---------------cut here---------------end--------------->8---
Would anyone with some insight of bap's internal please give me
some pointer to start debugging this?
Kind regards,
Phong
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 687 bytes --]
reply other threads:[~2024-08-09 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3B895OQFPEU.3LN72IL730XK5@guix \
--to=bug-guix@gnu.org \
--cc=72535@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=mcsinyx@disroot.org \
--cc=simon.tournier@u-paris.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).