I think it isn't possible for anyone to give you a definitive answer with only a GDB backtrace and no code/description. It looks like the 'this' pointer is NULL for your map iterator. I kind of doubt that's a GCC error though.
On Wed, Mar 14, 2012 at 8:23 AM, Iordan Alexandru <air...@yahoo.com> wrote: > > Hello > > I added a pseudo instruction to GEM5 and I want to dump the function > profile every time this pseudo-inst is called from my simulated > application. The problem is that my FS simulation ends with a segmentation > fault error. The backtrace in GDB shows the following: > > #0 _Rb_tree_const_iterator (this=0x0, tc=0x94d8208, os=...) at > build/ALPHA_FS/cpu/profile.cc:157 > #1 end (this=0x0, tc=0x94d8208, os=...) at > /usr/include/c++/4.5/bits/stl_tree.h:646 > #2 end (this=0x0, tc=0x94d8208, os=...) at > /usr/include/c++/4.5/bits/stl_map.h:335 > #3 FunctionProfile::dump (this=0x0, tc=0x94d8208, os=...) at > build/ALPHA_FS/cpu/profile.cc:126 > #4 0x083b1240 in SimpleThread::dumpFuncProfile (this=0x94d7bf8) at > build/ALPHA_FS/cpu/simple_thread.cc:227 > #5 0x0818673f in PseudoInst::wool_func (tc=0x94d8208, sc_by=0, task_id=60) > at build/ALPHA_FS/sim/pseudo_inst.cc:408 > #6 0x080a344b in AlphaISAInst::M5reserved2::execute (this=0xb2ba728, > xc=0x94d6f50, traceData=0x0) > at build/ALPHA_FS/arch/alpha/atomic_simple_cpu_exec.cc:11641 > #7 0x083d0006 in AtomicSimpleCPU::tick (this=0x94d6f50) at > build/ALPHA_FS/cpu/simple/atomic.cc:619 > #8 0x08141fb5 in EventQueue::serviceOne (this=0x8acdac8) at > build/ALPHA_FS/sim/eventq.cc:204 > #9 0x0817d72f in simulate (num_cycles=9223372036854775807) at > build/ALPHA_FS/sim/simulate.cc:72 > #10 0x0821f94d in _wrap_simulate__SWIG_0 (self=0x0, args=0xb79d60ac) > at build/ALPHA_FS/python/swig/event_wrap.cc:4534 > #11 _wrap_simulate (self=0x0, args=0xb79d60ac) at > build/ALPHA_FS/python/swig/event_wrap.cc:4584 > #12 0x001c531a in PyCFunction_Call () from /usr/lib/libpython2.7.so.1.0 > #13 0x0022c3a9 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 > #14 0x0022e4c8 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 > #15 0x0022c722 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 > #16 0x0022ccc3 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 > #17 0x0022e4c8 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 > #18 0x0022e623 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 > #19 0x0022caae in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 > #20 0x0022e4c8 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 > #21 0x0022c722 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 > #22 0x0022e4c8 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 > #23 0x0022e623 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 > #24 0x0024f31e in PyRun_StringFlags () from /usr/lib/libpython2.7.so.1.0 > #25 0x0814b8a9 in m5Main (argc=10, argv=0xbffff384) at > build/ALPHA_FS/sim/init.cc:256 > #26 0x0804e202 in main (argc=10, argv=0xbffff384) at > build/ALPHA_FS/sim/main.cc:57 > > Is this a GCC version problem? Has anybody any idea how to solve this? > > Thanks in advance! > > Alexandru Iordan > > _______________________________________________ > 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
