On Mon, 27 Aug 2012, Cookie wrote:
Hi Nilay,
I used "$scons build/X86/gem5.fast RUBY=True PROTOCOL=MOESI_hammer " to
compile gem5 and ran it with "$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
Hi Nilay,
I used "$scons build/X86/gem5.fast RUBY=True PROTOCOL=MOESI_hammer " to
compile gem5 and ran it with "$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 --ruby
--checkpoint-dir=checkpoint-di
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
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
Well, whenever I get a segmentation fault with any program, I run it under
GDB and figure out where the problem might be. In almost all the cases,
this works out well. You might also want to do the same.
--
Nilay
On Thu, 23 Aug 2012, Cookie wrote:
To whom it may concern,
I got segmentation
