Latest trinity from git is constantly complaining: [32492] Random reseed: 3901037224 msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. [watchdog] 200253 iterations. [F:161784 S:38468] msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. trinity: malloc.c:3616: _int_malloc: Assertion `(unsigned long)(size) >= (unsigned long)(nb)' failed. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive. msgrcv (70) returned ENOSYS, marking as inactive.
Whats up? I collected bunch of cores with -D and see this a lot, related perhaps: Core was generated by `./trinity -q -l off -C40 -D'. Program terminated with signal 11, Segmentation fault. #0 mkcall (childno=childno@entry=1) at syscall.c:292 292 syscalls_32bit[call32].entry->flags &= ~ACTIVE; #0 mkcall (childno=childno@entry=1) at syscall.c:292 #1 0x0000000000407e8c in do_random_syscalls (childno=childno@entry=1) at random-syscalls.c:125 Tommi -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
