[gem5-users] Fast Forwardiing Leads to a segmentation fault

[Abdlerhman Abotaleb via gem5-users]

I want to do a fast forwarding. i.e. run most of the source with AtomicSimpleCPU till encounter "m5_switch_cpu" then use Minor CPU. I used the following options when running GEM5 binary: "--cpu-type MinorCPU --fast-forward=1000000000000000000" I got a segmentation fault, and when debugging it with GDB it turns out to have this segmentation at tick 0 when try to initialize MinorCPU which is the future class CPU! I'm using se.py Another thing , should I expect that the after switch the CPU, it will use the cache subsystem as set in GEM5 options and the new CPU can use any data in memory written by the old CPU ? Thank you.

_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org