I'm not going to be able to debug it for you. You're going to need to figure out why your program is trying to use a NULL pointer.
Gabe On 11/30/11 01:12, Mahmood Naderan wrote: > Ok. > For one application, the gdb backtrace shows > > #0 0x00007ffff63f9a75 in *__GI_raise (sig=<value optimized out>) > at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x00007ffff63fd5c0 in *__GI_abort () at abort.c:92 > #2 0x0000000000c7ce15 in __exit_message (prefix=<value optimized > out>, code=-1, > func=<value optimized out>, file=<value optimized out>, line=292, > fmt=<value optimized out>, > a01=..., a02=..., a03=..., a04=..., a05=..., a06=..., a07=..., > a08=..., a09=..., a10=..., > a11=..., a12=..., a13=..., a14=..., a15=..., a16=...) at > build/X86_SE/base/misc.cc:84 > #3 0x00000000006e3569 in X86ISA::PageFault::invoke (this=<value > optimized out>, > tc=<value optimized out>, inst=<value optimized out>) at > build/X86_SE/arch/x86/faults.cc:292 > #4 0x0000000000e9b229 in BaseSimpleCPU::advancePC (this=0x1ea7720, > fault=<value optimized out>) > at build/X86_SE/cpu/simple/base.cc:498 > #5 0x0000000000e8d224 in AtomicSimpleCPU::tick (this=0x1ea7720) > at build/X86_SE/cpu/simple/atomic.cc:592 > #6 0x0000000000676154 in EventQueue::serviceOne (this=<value > optimized out>) > at build/X86_SE/sim/eventq.cc:204 > #7 0x00000000006bfbd2 in simulate (num_cycles=50000000000) at > build/X86_SE/sim/simulate.cc:73 > #8 0x00000000004392ad in _wrap_simulate__SWIG_0 (self=<value > optimized out>, args=0x1c84690) > at build/X86_SE/python/swig/event_wrap.cc:4447 > #9 _wrap_simulate (self=<value optimized out>, args=0x1c84690) > at build/X86_SE/python/swig/event_wrap.cc:4497 > > > > > > and the ExecAll flag shows: > 41956000: system.cpu + A0 T0 : > @_ZN9regmngobj13findfreeplaceEiiRiS0_+491.0 : ADD_R_R : add esi, > esi, r13d : IntAlu : D=0x0000000000000064 > 41958000: system.cpu + A0 T0 : > @_ZN9regmngobj13findfreeplaceEiiRiS0_+494 : movsxd rsi, rsi > 41958000: system.cpu + A0 T0 : > @_ZN9regmngobj13findfreeplaceEiiRiS0_+494.0 : MOVSXD_R_R : sexti > rsi, rsi, 0x1f : IntAlu : D=0x0000000000000000 > 41959000: system.cpu + A0 T0 : > @_ZN9regmngobj13findfreeplaceEiiRiS0_+497 : movzx ecx, > DS:[2*rsi + rcx] > 41959000: system.cpu + A0 T0 : > @_ZN9regmngobj13findfreeplaceEiiRiS0_+497.0 : MOVZX_W_R_M : ld > t1w, DS:[2*rsi + rcx] : MemRead : A=0x0 > panic: Tried to read unmapped address 0. > @ cycle 41959000 > -- > // Naderan *Mahmood; > > > On Tue, Nov 29, 2011 at 11:39 PM, Gabriel Michael Black > <[email protected] <mailto:[email protected]>> wrote: > > It means your program segfaulted, basically. There could be many > different causes. You'll have to debug it to find out what's going on. > > Gabe > > > Quoting Mahmood Naderan <[email protected] > <mailto:[email protected]>>: > > I get this error for some other benchmarks for some other > addresses. > Can someone clarify what does this annoying error mean? > > What is the root? > -- > // Naderan *Mahmood; > > > On Thu, Nov 24, 2011 at 5:37 PM, Mahmood Naderan > <[email protected] <mailto:[email protected]>>wrote: > > The same error appears when I try to resume from a checkpoint. > > 986885000: system.cpu T0 : @memcpy+121.1 : JNZ_I : limm > t2, > 0xffffffffffffffe5 : IntAlu : D=0xffffffffffffffe5 > 986886000: system.cpu T0 : @memcpy+121.2 : JNZ_I : wrip > , t1, t2 > : IntAlu : > 986887000: system.cpu T0 : @memcpy+123.0 : RET_NEAR : > ld t1, > SS:[rsp] : MemRead : D=0x0000000000000000 A=0x7fffffffebf8 > 986888000: system.cpu T0 : @memcpy+123.1 : RET_NEAR : > addi rsp, > rsp, 0x8 : IntAlu : D=0x00007fffffffec00 > 986889000: system.cpu T0 : @memcpy+123.2 : RET_NEAR : > wripi , t1, > 0 : IntAlu : > panic: Tried to execute unmapped address 0. > @ cycle 986890000 > [invoke:build/X86_SE/arch/x86/faults.cc, line 292] > > > > looking for any suggestion. > regards, > > On 11/12/11, Mahmood Naderan <[email protected] > <mailto:[email protected]>> wrote: > > Dear all, > > With X86_SE is in fast forward mode, I get this error: > > > > panic: Tried to read unmapped address 0. > > @ cycle 44265000 > > [invoke:build/X86_SE/arch/x86/faults.cc, line 292] > > > > > > turnning on the debugger with: > > build/X86_SE/m5.debug --debug-flags=Exec .... > > > > The trace shows: > > 44250000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+472.0 : JNLE_I > : rdip t1, > > %ctrl153, : IntAlu : D=0x000000000040251e > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+472.1 : JNLE_I > : limm t2, > > 0xfffffffffffffed2 : IntAlu : D=0xfffffffffffffed2 > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+472.2 : JNLE_I > : wrip , t1, > > t2 : IntAlu : > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+478.0 : MOV_R_M > : ld esi, > > DS:[rbx + 0x14c] : MemRead : D=0x0000000000000000 > A=0x6c10cc > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+484.0 : MOV_R_M > : ld rcx, > > DS:[rbx] : MemRead : D=0x0000000000000000 A=0x6c0f80 > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+487.0 : > IMUL_R_R : mul1s > > t17d, esi, r12d : IntAlu : D=0x0000000000000064 > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+487.1 : > IMUL_R_R : mulel > > esi, t17d, : IntAlu : D=0x0000000000000000 > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+487.2 : > IMUL_R_R : muleh > > t0d, t18d, : IntAlu : D=0x0000000000000000 > > > > 44251000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+491.0 : ADD_R_R > : add esi, > > esi, r13d : IntAlu : D=0x0000000000000064 > > > > 44252000: system.switch_cpus T0 : > > @_ZN9regmngobj13findfreeplaceEiiRiS0_+494.0 : > MOVSXD_R_R : sexti > > rsi, rsi, 0x1f : IntAlu : D=0x0000000000000000 > > > > panic: Tried to read unmapped address 0. > > @ cycle 44265000 > > [invoke:build/X86_SE/arch/x86/faults.cc, line 292] > > > > > > Can someone help to see what it the fault? > > > > -- > > // Naderan *Mahmood; > > > > > -- > -- > // Naderan *Mahmood; > > > > > _______________________________________________ > gem5-users mailing list > [email protected] <mailto:[email protected]> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
