amulecmd crashes with exit status 139. We confirmed the crash by
re-running it in a fresh debian unstable installation.

The attachment [1] contains a testcase (under ./crash) crashing the
program. It ensures that you can easily reproduce the bug. Additionally,
under ./crash_info/, we include more information about the crash such as
a core dump, the dmesg generated by the crash, and its output.

Regards,
The Mayhem Team (Alexandre Rebert, Thanassis Avgerinos, Sang Kil Cha, David Brumley, Manuel Egele)
Cylab, Carnegie Mellon University

[1] http://www.forallsecure.com/bug-reports/e48c8cdc3dd8e2266493706222f960861a2601bb/full_report

Hi,

I ran amulecmd 1:3.1.0-2 with the exact arguments, standard input and empty
environment from the Mayhem report: it rejects the arguments with its usage
message and exits with status 255, without crashing, also with glibc's
malloc perturbation enabled. The crash no longer reproduces, so I'm closing
this bug.

Regards,
Sandro