On Wed, Oct 01, 2014 at 07:42:28PM +0200, Toralf Förster wrote: > JJust FWIW with current git tree of trinity I run into this : > > [child2:30294] <timed out> > [child2:30294] <timed out> > BUG!: unreachable! > > BUG!: 9 > BUG!: [30306] generate-args.c:fill_arg:367 > [child3:30301] <timed out> > [child3:30301] <timed out> > [child3:30316] <timed out> > BUG!: unreachable! > > BUG!: 9 > BUG!: [30316] generate-args.c:fill_arg:367 > [child0:30306] trinity(show_backtrace+0x32) [0x80551f2] > > but I must admit this around the same time where the oom killer killed few tasks within the 32 bit KVM machine whre trintiy was fuzzying the kernel. This is really bad, something has scribbled over trinity's syscall definitions, and the type of the argument is garbage. Not enough info to really say what the cause of that was, whether it was a trinity bug, or uml bug. Hm, I wonder if it's worth mprotect(PROT_READ)'ing trinity's core structures that become read-only after setup. Dave -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
