> 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.
We had similar problems with ASIM many moons ago. It seems to me that we should really have a wrapper script for sanitizing the stack. Something as simple as: #!/bin/sh exec /usr/bin/env -i $* Unfortunately, that's not perfect since we do have a few environment variables that we use and we also pass arguments on the command line. Both of which are not fixed length. That said, the SCons environment is massive compared to most user environments. Using a wrapper script, we could prune both massively. Nate _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
