bap is missing all subcommands

  • Open
  • quality assurance status badge
Details
One participant
  • Nguyễn Gia Phong
Owner
unassigned
Submitted by
Nguyễn Gia Phong
Severity
normal

Debbugs page

Nguyễn Gia Phong wrote 7 months ago
(address . bug-guix@gnu.org)(address . julien@lepiller.eu)(address . simon.tournier@u-paris.fr)
D3B895OQFPEU.3LN72IL730XK5@guix
Hello Guix,

I noticed that bap (binary analysis platform)'s executable
is missing all subcommands:

Toggle snippet (35 lines)
$ 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.

Would anyone with some insight of bap's internal please give me
some pointer to start debugging this?

Kind regards,
Phong
-----BEGIN PGP SIGNATURE-----

iQHIBAABCAAyFiEE6Q4RuASTNDthMuOUJxSLLAaiIksFAma10WEUHG1jc2lueXhA
ZGlzcm9vdC5vcmcACgkQJxSLLAaiIkv3cwwAh6kwjYAYepUeEe2XEMDRRcPUugHw
9eIqESAtvGNy+y8PlTdEA21AzdQ2bg0n1NBuctYaGG44w9Iq2VdkUoj8rp2WoE80
zcGtoeKn/DkdxXeGAyquRsJyeAoJu5jfjvxDdK759BNGUTlLTTyZY0SDuaJTGHAM
PBTYJtfijPJJsHd6Qein1ZTLCgcPtwGWnjyKsnNKJgO94zPCbZs76HJTXWQlOi/h
eD7+rwzgy0gjpgMZY6FnW3JcWG4T5JswESjFAW2Z6HubhpW5TfzTXhAKUGs4h92g
GbCJSGrHQM01iwClZYRvx+kijuF+ZqJ7YUrw3uw6aVuVFaDeVJviUnKlz3snTOl9
Zljs2B9CXwkQYHHToGE8CJIrjxnjUC1ynXZyD1TrJk9nfhL2VKoVu5XhBVfmw4qN
dmPvEKTkgmJ71wAXwJDHLlsmP1+HIKpTcP0oU/4aI80ymZ+WkA/lTvXdksCEZ0N6
yRNtt4eTQ4T54J/5HhrQNudNcdxZgF3rmLHa
=JgY3
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 72535@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 72535
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help