On Fri, 24 Aug 2012, Cookie wrote:
Hi Nilay,
Thank you for your reply. I did debug it with gdb and it reported the
assertion "assert(isDeadlockEventScheduled() == false)" in
mem/ruby/system/RubyPort.cc was failed. I've no idea how to fix it but just
commented this statement and compiled and ran again. It reported
segmentation fault again because "build/X86/python/swig/pyevent.cc:84: void
cleanupCountedDrain(Event*): Assertion `event->getCount() == 0' failed."
I would not be able to debug unless I can reproduce the situation.
Just reading the code did made feel that something is incorrect.
I also tried to restore the checkpoints (they seemed to be created, at
least there were checkpoint files in the directory) using the following
command: build/X86/m5.debug -d ruby-output configs/example/ruby_fs.py
--kernel=x86_64-vmlinux-2.6.22.9.smp --script=configs/boot/mcf.rcS
--cpu-type=detailed --caches --ruby -r 4.
But it failed and reported as:
----------------------
File "/home/ytian/Documents/Gem5/configs/common/Simulation.py", line 70,
in setCPUClass
class TmpClass(AtomicSimpleCPU): pass
NameError: global name 'AtomicSimpleCPU' is not defined
------------------------
So I removed the option "--cpu-type" and used "--restore-with-cpu=detailed"
to restore the checkpoint again. It reported as:
-----------------------
File "/home/ytian/Documents/Gem5/configs/common/Simulation.py", line 45,
in setCPUClass
class TmpClass(TimingSimpleCPU): pass
NameError: global name 'TimingSimpleCPU' is not defined
------------------------
I think both of the objects are defined. So I wonder if there is something
wrong with the steps/options which I used to compile/run the gem5 since I
didn't make any changes to the source code. Could you please help me fix
this problem? Thank you for your help.
What command and configuration file did you use for compilation?
--
Nilay
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
