using m5.debug
Program received signal SIGSEGV, Segmentation fault.
0x000000000046d18c in Port::sendTiming (this=0x0, pkt=0x3081120) at
build/X86_SE/mem/port.hh:186
186 bool sendTiming(PacketPtr pkt) { return peer->recvTiming(pkt); }
(gdb) bt
#0 0x000000000046d18c in Port::sendTiming (this=0x0, pkt=0x3081120)
at build/X86_SE/mem/port.hh:186
#1 0x0000000000473853 in Bus::recvTiming (this=0x233c480,
pkt=0x3081120) at build/X86_SE/mem/bus.cc:265
#2 0x000000000047b66f in Bus::BusPort::recvTiming (this=0x25a5360,
pkt=0x3081120) at build/X86_SE/mem/bus.hh:89
#3 0x000000000046d1ae in Port::sendTiming (this=0x24798f0,
pkt=0x3081120) at build/X86_SE/mem/port.hh:186
#4 0x00000000005d2db0 in Cache<LRU>::MemSidePort::sendPacket
(this=0x24798f0) at build/X86_SE/mem/cache/cache_impl.hh:1746
#5 0x00000000005d4185 in Cache<LRU>::MemSidePort::recvRetry
(this=0x24798f0) at build/X86_SE/mem/cache/cache_impl.hh:1785
#6 0x000000000047b595 in Port::sendRetry (this=0x25a5360) at
build/X86_SE/mem/port.hh:212
#7 0x0000000000474a32 in Bus::recvRetry (this=0x233c480, id=-1) at
build/X86_SE/mem/bus.cc:305
#8 0x00000000004725f3 in Bus::BusFreeEvent::process (this=0x233c568)
at build/X86_SE/mem/bus.cc:129
#9 0x000000000065856c in EventQueue::serviceOne (this=0x17876c0) at
build/X86_SE/sim/eventq.cc:204
#10 0x000000000069c31c in simulate (num_cycles=385696971000) at
build/X86_SE/sim/simulate.cc:74
On 1/22/12, Nilay Vaish <ni...@cs.wisc.edu> wrote:
> The segmentation fault occurred in the code for the bus, not in the atomic
> cpu. It seems you are not using gem5.debug. If you are debugging with gdb,
> try to use gem5.debug, the back trace output will be better.
>
> --
> Nilay
>
> On Sun, 22 Jan 2012, Mahmood Naderan wrote:
>
>> Hi,
>> I get segmentation fault in atomic simplpe cpu (before switching to
>> O3). The backtrace shows:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> Bus::recvAtomic (this=<optimized out>, pkt=0x252e5a8) at
>> build/X86_SE/mem/bus.cc:673
>> 673 }
>> (gdb) bt
>> #0 Bus::recvAtomic (this=<optimized out>, pkt=0x252e5a8) at
>> build/X86_SE/mem/bus.cc:673
>>
>> #1 0x00000000005e5bd5 in sendAtomic (pkt=0x252e5a8, this=<optimized
>> out>) at build/X86_SE/mem/port.hh:194
>>
>> #2 Cache<LRU>::atomicAccess (this=0x21f5b20, pkt=0x252ecf8) at
>> build/X86_SE/mem/cache/cache_impl.hh:746
>>
>> #3 0x000000000049bc25 in sendAtomic (pkt=0x252ecf8, this=<optimized
>> out>) at build/X86_SE/mem/port.hh:194
>>
>> #4 Bus::recvAtomic (this=<optimized out>, pkt=0x252ecf8) at
>> build/X86_SE/mem/bus.cc:428
>>
>> #5 0x00000000005e5bd5 in sendAtomic (pkt=0x252ecf8, this=<optimized
>> out>) at build/X86_SE/mem/port.hh:194
>>
>> #6 Cache<LRU>::atomicAccess (this=0x2322330, pkt=0x7fffffffc8c0) at
>> build/X86_SE/mem/cache/cache_impl.hh:746
>>
>> #7 0x000000000086421e in sendAtomic (pkt=0x7fffffffc8c0,
>> this=<optimized out>) at build/X86_SE/mem/port.hh:194
>>
>> #8 AtomicSimpleCPU::writeMem (this=0x2251f30, data=0x7fffffffcb90
>> "\034\307q\034\307q\234?\020\320\377\377\377\177", size=8,
>> addr=46912763695104, flags=3, res=0x0) at
>> build/X86_SE/cpu/simple/atomic.cc:457
>>
>> #9 0x0000000000c59f74 in writeMemTiming<AtomicSimpleCPU>
>> (flags=<optimized out>, addr=<optimized out>,
>> dataSize=<optimized out>, mem=4583663620745971484, traceData=0x0,
>> xc=0x2251f30, res=<optimized out>)
>> at build/X86_SE/arch/x86/memhelpers.hh:113
>>
>> #10 writeMemAtomic<AtomicSimpleCPU> (flags=<optimized out>,
>> addr=<optimized out>, dataSize=<optimized out>,
>> mem=<optimized out>, traceData=0x0, xc=0x2251f30, res=<optimized
>> out>) at build/X86_SE/arch/x86/memhelpers.hh:122
>>
>> #11 X86ISAInst::St::execute (this=0x2e460b0, xc=0x2251f30, traceData=0x0)
>> at build/X86_SE/arch/x86/atomic_simple_cpu_exec.cc:13756
>>
>> #12 0x00000000008649df in AtomicSimpleCPU::tick (this=0x2251f30) at
>> build/X86_SE/cpu/simple/atomic.cc:567
>>
>> #13 0x000000000067e04e in EventQueue::serviceOne (this=<optimized
>> out>) at build/X86_SE/sim/eventq.cc:204
>>
>> #14 0x00000000006bd47a in simulate (num_cycles=9223372036854775807) at
>> build/X86_SE/sim/simulate.cc:74
>>
>>
>> I have not changed atomic cpu model so please share any suggestion.
>> What is the description of this fault?
>>
>> --
>> // Naderan *Mahmood;
>> _______________________________________________
>> gem5-users mailing list
>> gem5-users@gem5.org
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
--
--
// Naderan *Mahmood;
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
