On Fri, Jan 10, 2014 at 04:46:05PM +0000, Elliott, Robert (Server Storage) wrote: > 3. The assert does not trigger, and the same crash occurs as before. > > C:\Users\Administrator\fio>c:\cygwin64\bin\gdb -args "c:/program > files/fio/fio.exe" --filename=rob.tmp --size=128m --direct=1 --rw=randread > --refill_buffers --norandommap --randrepeat=0 --bs=4k --iodepth=16 > --numjobs=16 --runtime=60 --group_reporting --name=4ktest --time_based > Jobs: 0 (f=0) > Program received signal SIGSEGV, Segmentation fault. > 0x0000000064943236 in pthread_mutex_unlock () > from /cygdrive/c/program files/fio/libwinpthread-1.dll
I've finally had time to reproduce this on a Windows 7 box. I use a different command line: ./fio.exe --debug=all --filename=fiojob --thread --size=512 --rw=read --bs=512 --ioengine=sync --verify_pattern=0xdeadbeef --name=fiojobname The problem appears to be that the mutex is being destroyed while it is still being held by a different thread. Adding return; to the first line of fio_mutex_remove in mutex.c papers over the problem... -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
