> I have run this through gdb in with m5.debug and see the same errors, the > problem is the stack trace showing the cause of the seg fault or assert > changes depending on the inputs to the simulator. So, I have not been able > to pin point this bug which appears to be a subtle memory corruption > somewhere in the code. This error does not happen for other trace flags such > as the “Cache” trace flag. It appears linked solely to the instruction > tracing mechanism. Has anybody else seen this bug?
Regressions have been passing and I haven't heard anything about this, so we'll need more info. (Or better yet, I'd like to give you moral support to continue debugging :) Nate _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
