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
I would echo Gabe sentiments. I've been suspicious of the trace-flags
causing memory corruption for awhile now, but every time I dig into it
there's some small error that I'm propagating through that finally surfaces.
In the big picture, I suspect that the trace-flags just exacerbate any kind
of
I tried that command line and I haven't seen any segfault yet. I'll let
it run and see if anything happens. What version of the code are you using?
Gabe
Geoffrey Blake wrote:
I’ve added a couple edits, but nothing major, ie: added statistics to
the bus model, and some extra latency
