Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invocation instructions should specify expected result #149

Open
hmeine opened this issue Jun 3, 2021 · 1 comment
Open

Invocation instructions should specify expected result #149

hmeine opened this issue Jun 3, 2021 · 1 comment

Comments

@hmeine
Copy link

hmeine commented Jun 3, 2021

Hi, I am trying to get BANG to work, believing that it's a tool that could be very useful, but I have not had a lot of success with it yet.

  1. The first invocation on a large (saved) docker image led to a lot of output, but then BANG would apparently hang. (I may open a separate issue about this.)
  2. I then tried with a much smaller, simpler docker image, and got no errors and no hang. Yet… I wonder what I output I should expect, and where? (There are only lines that look like filenames / image contents.) I could not find any created log file or report, for instance.

Since I used the command listed in the README, I would suggest to put a sentence below that (in the "Invocation" section) what kind of output one should expect.

@armijnhemel
Copy link
Owner

Thanks, I will look into this ASAP. Documentation is something that needs to be improved.

hmeine added a commit to hmeine/binaryanalysis-ng that referenced this issue Jun 3, 2021
Since BANG is by default writing output to `~/tmp` and not to the current directory, it may easily happen that a new user wonders where to look for the resulting report. (See issue armijnhemel#149)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants