The execution trace enabled by --debug-flag is intended for debugging, not as a way to record an execution trace, so all the output goes to a single file. If you want it split by thread you'd have to take that output and run it through another program (like multiple instances of grep, or a short perl script, or maybe some obscure unix utility I don't know about).
If you want to record a trace for replay later, there might be better ways, depending on how much effort you want to put into it. Others on the list might have some suggestions. Steve P.S. This discussion really belongs on the gem5-users list, so I moved it there. Also, please don't quote big digest articles when posting. On Thu, Sep 20, 2012 at 10:03 AM, Yanqi Zhou <yan...@princeton.edu> wrote: > By turning on the trace file flag, gem5 generate dynamic execution file. > When do multithreading, there should be multiple trace files generated, but > it is not the case in my simulation. Is there a way to generate multiple > trace files? > >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
