I can't tell if this is just a gdb quirk because I haven't hand built winpthreads but: Program received signal SIGSEGV, Segmentation fault. 0x0043e1de in pthread_mutex_unlock (m=0x790000) at /usr/src/debug/mingw64-i686-winpthreads-3.1.0-1/src/mutex.c:392 (gdb) list Line number 392 out of range; /usr/src/debug/mingw64-i686-winpthreads-3.1.0-1/src/mutex.c has 228 lines. As Elliott mentioned the windowaio engine doesn't exhibit this problem (but perhaps it causes different thread scheduling?)... On Tue, Feb 11, 2014 at 08:38:46AM -0700, Jens Axboe wrote: > Interesting. The mutex issue should be fixed, I'm puzzled why it isn't. > And especially if the sync ioengine has something to do with it. Can > either of you dump the source around: > > at > /usr/src/debug/mingw64-i686-winpthreads-3.1.0-1/src/mutex.c:392 > > perhaps that will clear things up a bit more? > > On Tue, Feb 11 2014, Elliott, Robert (Server Storage) wrote: > > That specific command line does also crash on my Windows 2008 R2 system. It does not crash if I drop --ioengine=sync. > > > > > -----Original Message----- > > > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On > > > Behalf Of Sitsofe Wheeler > > > > > > $ gdb --args ./fio.exe --debug=all --filename=fiojob --thread --size=512 -- > > > rw=re > > > ad --bs=512 --ioengine=sync --verify_pattern=0xdeadbeef -- > > > name=fiojobname -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
