search

angr / tracer

Utilities for generating dynamic traces
BSD 2-Clause "Simplified" License
88 stars 28 forks source link

issue with running tracer for a cgc binary #29

Closed benquike closed 7 years ago

benquike commented 7 years ago

When running Tracer with this binary, KPRCA_00034_patched, with this file id:000000,sig:11,src:000157,op:havoc,rep:4.zip, the following exception happpens.

IndexError: list index out of range

And the reason is that when the tracer runs that binary, shellphish-qemu-cgc-tracer exits with the following error.

Error while loading /export/users/cgc-vm_fuzz/cgc-challenge-corpus/KPRCA_00034/bin/KPRCA_00034_patched: Operation not permitted
salls commented 7 years ago

Can you check the permissions on the binary? make sure it's executable

benquike commented 7 years ago

Yes, it has x permission

benquike commented 7 years ago

I found that it is caused by the -magicdump option. If the file specified by the argument exists, this issue will happen.

benquike commented 7 years ago

I finally figured out what was wrong.

zardus commented 7 years ago

Would you mind writing a quick blurb about the cause to help future sufferers?

On Jul 20, 2017 5:00 PM, "Hui Peng" notifications@github.com wrote:

Closed #29 https://github.com/angr/tracer/issues/29.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/angr/tracer/issues/29#event-1173077978, or mute the thread https://github.com/notifications/unsubscribe-auth/ADSzl4mkN0XoFLgyMTQlJXLnqNyFLtg3ks5sP-ovgaJpZM4OWXpU .

benquike commented 7 years ago

@zardus It was that the directory for storing the qemu trace logs ran out of space. Because previous runs of tracer exited in an code path in which the trace log was not removed and the logs accumulated .... finally all the space was eated up