Hi all,
When running a trace to debug a problem that triggers an assertion,
I've tried outputting a compressed format. Unfortunately, it seems that
the file is closed improperly, resulting in a corrupt trace. This can be
seen easily by trying to zcat the tail of the file. It seems like their
should be a hook to let the compressed file close correctly before exiting
gem5 after an assertion is triggered. Is anyone familiar with where and
how this is currently done in the source code?
Thanks,
Andrew
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
