According to the document, there is an M5 pseudo instruction inside the benchmark that causes the checkpoint to be created. You are correct. The segmentation fault is reached before that pseudo instruction is reached. The cause of segmentation fault is glibc version 2.3.4 which is older than the recommended version.
On Thu, Nov 29, 2012 at 3:30 AM, Nilay Vaish <[email protected]> wrote: > On Thu, 29 Nov 2012, Sumit Dhoble wrote: > >> Contents of the auto-generated script : >> >> #!/bin/sh >> >> # File to run the bodytrack benchmark >> >> cd /parsec/install/bin.ckpts >> /sbin/m5 dumpstats >> /sbin/m5 resetstats >> ./bodytrack /parsec/install/inputs/bodytrack/sequenceB_1 4 1 1000 5 0 3 >> echo "Done :D" >> /sbin/m5 exit >> /sbin/m5 exit >> >> > > Why do you expect this script to create a checkpoint? Does the program > bodytrack itself includes a checkpoint instruction? If yes, then that means > the instruction is never reached. > > -- > Nilay _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
