> > > The difference > between running gem5 in SCons and running it with a subprocess call is > the environment that is present when gem5 starts (what is on the initial > stack mostly). It's likely that the stack differences is causing the > output to change and it's not SCons fault directly. >
That's my primary (only?) hypothesis, too, but it still seems very weird that the "alternate" results only show up in this one very specific case (one invocation method on one machine). It seems like if it really was a stack size/alignment issue that we'd be seeing inconsistent results on more than one machine. Steve _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
