On Thu, 10 Jan 2013, Yiding Han wrote:
Hi,
As a new user, I am running the latest version of gem5 on CentOS 6. I want
to simulate the SPEC2k6 benchmarks with a X86 architecture. I compiled
./build/X86/gem5.opt without any issue. The SPEC2k6 benchmarks are all
compiled with -static flags, which can run in SE mode successfully with my
scripts modified from this page:
http://www.m5sim.org/SPEC_CPU2006_benchmarks
I generate the checkpoint with:
./build/X86/gem5.opt configs/cmp.py -b perlbench
--take-checkpoint=500000000,100000000 --max-checkpoint=1
--checkpoint-dir=./m5out/checkpoint/400.perlbench/
It seems to work since a checkpoint is written. Although gem5 seems to have
issues exiting the simulation:
Global frequency set at 1000000000000 ticks per second
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
info: Entering event queue @ 0. Starting simulation...
warn: instruction 'fldcw_Mw' unimplemented
Writing checkpoint
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/users/home/yiding/gem5/gem5/src/python/m5/main.py", line 359, in
main
exec filecode in scope
File "configs/cmp.py", line 147, in <module>
Simulation.run(options, root, system, FutureClass)
File "/users/home/yiding/gem5/gem5/configs/common/Simulation.py", line
506, in run
print 'Exiting @ tick %i because %s' % (m5.curTick(),
exit_event.getCause())
UnboundLocalError: local variable 'exit_event' referenced before assignment
But the *real* issue is when I try to restore the checkpoint, gem5 has a
segfault:
./build/X86/gem5.opt configs/cmp.py -b perlbench --checkpoint-restore=1
--checkpoint-dir=./m5out/checkpoint/400.perlbench/
Global frequency set at 1000000000000 ticks per second
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
warn: optional parameter system.cpu.workload:M5_pid not present
**** REAL SIMULATION ****
info: Entering event queue @ 500000000. Starting simulation...
Segmentation fault
It seems that the segmentation fault occurred in gem5, and not the
application. It should be straight forward to figure out where the
segmentation fault occurred using gdb. Post the function call stack. It
should be possible to figure out the cause that.
--
Nilay
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
