Driller fails to generate new inputs

[qsphan]

As described in the title, driller fails to generate the new inputs for the following toy program (please remove .txt from all files, hello.txt is the binary). If you compile hello.c inside mechaphish container, driller does generate new inputs.

gcc version is gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406

drill.py.txt hello.c.txt hello.txt

[zardus]

To clarify:

• compile program inside container, run analysis outside --> successful generation of new inputs
• compile program outside of container, run analysis inside --> no inputs generated

Is that correct?

On Tue, Dec 5, 2017 at 5:18 PM Quoc-Sang Phan notifications@github.com wrote:

As described in the title, driller fails to generate the new inputs for the following toy program (please remove .txt from all files, hello.txt is the binary). If you compile hello.c inside mechaphish container, driller does generate new inputs.

gcc version is gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406

drill.py.txt https://github.com/shellphish/driller/files/1533162/drill.py.txt hello.c.txt https://github.com/shellphish/driller/files/1533163/hello.c.txt hello.txt https://github.com/shellphish/driller/files/1533164/hello.txt

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/shellphish/driller/issues/53, or mute the thread https://github.com/notifications/unsubscribe-auth/ADSzl7SEYUkCeNu3hhmOnEeKmxaO3i2uks5s9cEfgaJpZM4Q3DZi .

[qsphan]

@zardus No, analysis is always inside the container. In summary:

• compile program inside container, run analysis inside --> successful generation of new inputs (not sure about their correctness)
• compile program outside of container, run analysis inside --> no inputs generated