Hi Abhishek, Check --debug-help. You probably want --debug-file=<filename> and you may want --debug-start=<tick> when debugging Ruby protocols in FS mode. I've also found it useful to use a named pipe for the debug file and pipe it though `tail` to get only the last n lines (where n is usually megabytes to gigabytes).
PS: Using the Ruby random tester is a way to debug protocol issues without having to wait for hours (days if you have tracing on) for Linux to boot. Cheers, Jason On Mon, Apr 15, 2019 at 9:01 AM ABHISHEK BHATTACHARYYA < abhattach...@wisc.edu> wrote: > Hi > > I am running a full system simulation of gem5 with parsec benchmarks using > an rcs script. I have added new debug prints to the gem5 code to trace > RubySlicc request and response actions. How do I redirect the debug prints > to a new file and collect the trace in this case? > > Thanks, > Abhishek Bhattacharyya > > Regards, > > > Abhishek Bhattacharyya > > *Graduate Research Assistant* > > *Electrical and Computer Engineering Department* > > *University of Wisconsin-Madison* > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
