Thanks Paul. The location where the segfault is happening was located. Due to my negligence, the "memoryController_" instance was not initialized proper. Now the latest MarssX86 and DRAMSim2 are running well.
Program received signal SIGSEGV, Segmentation fault. 0x00000000005fdbd5 in Memory::MemoryHierarchy::clock (this=0x3368ba0) at ptlsim/build/cache/memoryHierarchy.cpp:100 100 ((MemoryController*)memoryController_)->mem->update(); (gdb) p memoryController_ $1 = (Memory::Controller *) 0x0 (gdb) 在2013-04-29 17:24:37，高珂[email protected]写道： There's not enough information here to figure out the problem. Can you build MARSS with debug=1 and libdramsim.so with DEBUG=1 and then run in gdb to figure out where the segfault is happening? On Sat, Apr 27, 2013 at 11:01 AM, 高珂 <[email protected]> wrote: Hi, all, I 'm going to integerate the latest Marss version with DRAMSim2 together (cuz .. marss.dramsim is out of date). After changing the ptlsim codes according marss.dramsim version , there was no problem in Emulation mode, but 'core dumped' happened as follows when switching to simuaiton mode. Could someone give me some tips to address this problem ? Thanks in advance . model file '../DRAMSim2/system.ini' == ===== MemorySystem 0 ===== CH. 0 TOTAL_STORAGE : 2048MB | 4 Ranks | 4 Devices per rank ===== MemorySystem 1 ===== CH. 1 TOTAL_STORAGE : 2048MB | 4 Ranks | 4 Devices per rank Completed 0 cycles, 0 commits: 0 Hz, 0 insns/sec: rip ffffffff81013092 ffffffff81013092 0000000000400aef ffffffff81013092 ffffffff81013092 ffffffff81013092 ffffffff81013092 ffffffff81013092Segmentation fault (core dumped) _______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
