On 06/09/15 16:45, Matthias Urlichs wrote: > Johan Ström <johan <at> stromnet.se> writes: >> Ok, very early crash then. Does it help buidling with --disable-zero? >> > Will try. > >> Do you have the gdb output from this as well? The above looks more like >> a syscall trace. >> > It is (by way of strace). > >> "thread apply all backtrace" is a useful gdb cmd to dump backtrace of >> all running threads. >> > Thanks; fortunately, doing that manually isn't too onerous when there are > only > two threads. > > Anyway, I assume that this is not the only box owfs crashes on, so if > somebody > else also sees something like this, I'd appreciate the help -- I do know my > way > around gdb, but I also need a couple of weeks that are not in the calendar …
You never know, thought it was better to be verbose and save one roundtrip of gdb-questions.. :) I've never had any crashes like that, running on FreeBSD with the following options: ./configure --enable-debug --enable-owlib --enable-owshell --enable-ownetlib --enable-owserver CFLAGS=-g --disable-zero --enable-owtraffic --disable-mutexdebug Johan ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
