Jason, > does anyone have an objection to changing the default behavior to > *print* the return code if it is not 0 and always have gem5 exit > with 0 regardless of the return code of the simulated binary?
That would be a very welcome change. We have a demo called "Nano" which I stopped showing because having to "echo @?" after gem5 exits, confuses people and completely kills the demo's effectiveness. Printing the return code at the end of the guest would be very cool. Boris -----"gem5-dev" <[email protected]> wrote: ----- To: gem5 Developer List <[email protected]> From: Jason Lowe-Power Sent by: "gem5-dev" Date: 09/21/2017 06:27PM Subject: [gem5-dev] ARM hello return code 13? Hi all, I'm working on getting the new testing infrastructure out and ran into an "interesting" problem. Right now, gem5's return code is the same as the return code of the application it is executing (in SE mode). Strangely, the 'hello' binary for ARM has a return code of 13. I verified this with a fresh binary on qemu as well. Any idea why the return code isn't 0? Also, does anyone have an objection to changing the default behavior to *print* the return code if it is not 0 and always have gem5 exit with 0 regardless of the return code of the simulated binary? Thanks, Jason _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
