OK, I've looked through logs of several runs and seems to me that 32bit faults look legit, they just doing something bad or hang the process and thus getting killed by the os or by watchdog. At the end of the day, if someone does not want to have such noise on x86_64 arch use "-a 64" argument to switch off all 32bit calls. On Wed, Oct 2, 2013 at 1:57 PM, Dave Jones <davej@xxxxxxxxxx> wrote: > On Wed, Oct 02, 2013 at 01:53:15PM -0700, Ildar Muslukhov wrote: > > Got it. I wonder, what are the settings you running the trinity > > yourself? Are you fuzzing all calls at the same time, or you limit > > your self to a set or one function at a time? > > depends. if I'm not looking for anything specific, I'll just fire off > scripts/test-multi.sh Once I've triggered something, I might narrow > it down with more specific parameters (see scripts/find.sh) for eg. > > Also sometimes I'll add something like -x perf_event_open or the like > to the scripts to avoid hitting certain bugs until they're fixed. > > Sometimes I'll remove the '-l off' if I want to try and pick through the logs > after hitting a bug. > > > 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
