-
Notifications
You must be signed in to change notification settings - Fork 14
Description
On a Mac M1 I built the CBAT Docker image and ran the container. All files appear to be present and I am able to run the various wp
analyses from the CBAT tutorial. However, they do not produce output, e.g., bap wp --func=main --trip-asserts 01/binary/main
should show "SAT! ..." but instead displays nothing. On the other hand, CBAT places an input in RDI that will trip the assert when I put the output in a .yml file and use it to initialize bildb
:
bap wp --func=main --trip-asserts --bildb-output=init.yml 01/binary/main
followed by
bap 01/binary/main --pass=run --run-entry-point=main --bildb-debug --bildb-init=init.yml
. This helps, but in some situations I need the standard wp
output.
(I don't know if the following is related, but the only atypical thing about my installation is that the Dockerfile resulted in an error at the stage cd cbat_tools/bildb; \ opam config exec -- make
. I could proceed by commenting out opam config exec -- make
and then modifying the Makefile in the /home/opam/cbat_tools/bildb
directory to comment out every mention of plugin.uninstall
. AFAICT, bildb
is working normally.)