Thanks for the report and sorry for the silent. I can only confirm ATM that even the most recent in 0.2.x series 0.2.13 is exhibiting the same issue:
$> ./crash.sh ./crash.sh: line 22: 22040 Segmentation fault env -i MALLOC_CHECK_=0 $GDB /usr/lib/mrtrix/bin/read_ximg "`cat $DIR/argv_1.symb`" "`cat $DIR/argv_2.symb`" "`cat $DIR/argv_3.symb`" < "$DIR/file___dev__stdin.symb" btw -- what tool was used to produce those bundles with the troubleshooting information etc (I guess it wasn't done manually) ? On Wed, 10 Jul 2013, Alexandre Rebert wrote: > Package: mrtrix > Version: 0.2.10-2 > Severity: normal > User: may...@forallsecure.com > Usertags: mayhem > read_ximg 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/94e4161bb7a57e7125482b1caaa83d8dc1240a2a/full_report -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
