Date: Sat, 23 Jun 2012 00:26:08 +0200 From: Frank Dittrich <frank_dittrich@...mail.com> To: john-dev@...ts.openwall.com Subject: $ ./john --test=0 segfaults on rar format (was: $ ./john --test=0 segfaults on wpapsk format for linux-x86-sse2 build) On 06/22/2012 11:48 PM, jfoug wrote: >> From: Frank Dittrich [mailto:frank_dittrich@...mail.com] >> >> So wpapsk is still broken in magnum-jumbo for linux-x86-sse2 (32bit). > > It works fine for me, on cygwin-sse and cygwin-ssei. OK, I rebuilt with debugging options, and this time I as lucky, I got the segfault even in gdb. If wasn't in wpapsk test (that's why, I couldn't reproduce. The segfault occurred in rar self test. (May be we should flush the buffers before starting the next self test. Then I would have seen that wpapsk completed, which I didn't now - judging from the output.) Here are the details: Program received signal SIGSEGV, Segmentation fault. 0x44ac2200 in malloc_consolidate.part.3 () from /lib/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.14.90-24.fc16.7.i686 keyutils-libs-1.5.2-1.fc16.i686 krb5-libs-1.9.3-2.fc16.i686 libcom_err-1.41.14-2.fc15.i686 libselinux-2.1.6-6.fc16.i686 nss-softokn-freebl-3.13.4-1.fc16.i686 openssl-1.0.0j-1.fc16.i686 zlib-1.2.5-6.fc16.i686 (gdb) bt #0 0x44ac2200 in malloc_consolidate.part.3 () from /lib/libc.so.6 #1 0x44ac3d87 in _int_malloc () from /lib/libc.so.6 #2 0x44ac6395 in malloc () from /lib/libc.so.6 #3 0x080e433b in mem_alloc (size=4249623) at memory.c:54 #4 0x080e4448 in mem_alloc_tiny (size=4249620, align=3) at memory.c:84 #5 0x080e4488 in mem_calloc_tiny (size=4249620, align=4) at memory.c:93 #6 0x08095bae in init (pFmt=0x8160880) at rar_fmt.c:666 #7 0x080dc90e in fmt_init (format=0x8160880) at formats.c:31 #8 0x080d66cc in benchmark_all () at bench.c:386 #9 0x080e0f8f in john_run () at john.c:831 #10 0x080e1591 in main (argc=2, argv=0xbffff2c4) at john.c:1042 rar_fmt.c:666 is unpack_data = mem_calloc_tiny(sizeof(unpack_data_t) * omp_t, MEM_ALIGN_WORD); Unfortunately, magnum will be away for a few days. I'll probably not have time right now to dig into it. Frank
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.