Hi Sparsh, Can you send me the stack trace so I can pin point exactly where its crashing. Also if possible send me the changes you have made. I looked at the code and it seems that while printing the memory request only one pointer can be cause this seg-fault, that is 'coreSignal_' variable. But before printing we check if it is null or not.
- Avadh On Fri, Sep 9, 2011 at 3:10 PM, sparsh1 mittal1 <[email protected]>wrote: > Hello > I am using shared l2 config for 2 core and wanted to know from which core, > a request is generated. > > While trying to print queueEntry->request in cacheController.cpp, > cache_access_cb function, I get segmentation fault. > > queueEntry->request->get_physical_address() is working fine, since that is > how L2 cache access address is generated. > > It means, the other parameters of MemoryRequest variable are not getting > initialized or something else. > > > $ qemu/qemu-system-x86_64 -m 1G -drive > file=/home/sparsh/cdrive/multicore/marss/parsecROIpersonal.qcow2,cache=unsafe > -simconfig twocore.cfg -loadvm fer_freq > initing the ooomachine > -stopinsns 1000 -stats fer_freq.stats -logfile fer_freq.log -kill-after-run > -yamlstats fer_freq.yaml -machine shared_l2_2core > MARSSx86::Command received : -run > Completed 0 cycles, 0 commits: 0 > Hz, 0 insns/sec: rip 00007f1cdfc2435d 000000000043753dSegmentation > fault > > Thanks and Regards > Sparsh Mittal > > > > _______________________________________________ > 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
