----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3293/#review7929 -----------------------------------------------------------
I support this feature being added - a question -- src/python/m5/main.py (lines 106 - 107) <http://reviews.gem5.org/r/3293/#comment6901> everything in this area of the code is metavar TICK, "at TICK", any reason to go with "TIME" here instead? - Curtis Dunham On Jan. 19, 2016, 11:03 p.m., Michael LeBeane wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3293/ > ----------------------------------------------------------- > > (Updated Jan. 19, 2016, 11:03 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11310:bc7702daf93e > --------------------------- > configs: add command-line option to stop debug output > > This patch adds a --debug-end flag to main.py so that debug output can be > stopped at a specified tick, while allowing the simulation to continue. > It is useful in situations where you would like to produce a trace for a > region of interest while still collecting stats for the entire run. This is > in contrast to the currently existing --debug-break flag, which terminates the > simulation at the tick. > > > Diffs > ----- > > src/python/m5/main.py 9be8a40026dfa419c3daf572407f9391ad48e1ed > > Diff: http://reviews.gem5.org/r/3293/diff/ > > > Testing > ------- > > > Thanks, > > Michael LeBeane > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
