On Mon, 4 Jul 2011, Mahmood Naderan wrote:
ok.
I attached the program to gdb
mahmood@srv:gem5$ gdb --arg build/ALPHA_FS/m5.debug
configs/example/fs.py --script=configs/parsec/runscript.rcS
....
Reading symbols from /home/mahmood/gem5/build/ALPHA_FS/m5.debug...done.
(gdb) b main
Breakpoint 1 at 0x409ab3: file build/ALPHA_FS/sim/main.cc, line 45.
(gdb) run
Starting program: /home/mahmood/gem5/build/ALPHA_FS/m5.debug
configs/example/fs.py --script=configs/parsec/runscript.rcS
[Thread debugging using libthread_db enabled]
Breakpoint 1, main (argc=3, argv=0x7fffffffe2c8) at
build/ALPHA_FS/sim/main.cc:45
45 initSignals();
(gdb) call schedBreakCycle(1800000000000)
warn: need to stop all queues
(gdb) c
Continuing.
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.
....
command line: /home/mahmood/gem5/build/ALPHA_FS/m5.debug
configs/example/fs.py --script=configs/parsec/runscript.rcS
....
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
warn: Prefetch instructions in Alpha do not do anything
warn: Prefetch instructions in Alpha do not do anything
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff63f9d57 in kill () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff63f9d57 in kill () from /lib/libc.so.6
#1 0x000000000084e89d in Debug::breakpoint () at
build/ALPHA_FS/base/debug.cc:56
#2 0x0000000000556d85 in DebugBreakEvent::process (this=0x136f1e0)
at build/ALPHA_FS/sim/debug.cc:71
#3 0x00000000005590f8 in EventQueue::serviceOne (this=0x133abb0)
at build/ALPHA_FS/sim/eventq.cc:204
#4 0x00000000005ac43f in simulate (num_cycles=9223372036854775807)
at build/ALPHA_FS/sim/simulate.cc:73
#5 0x0000000000446745 in _wrap_simulate__SWIG_0 (args=0x1c0c4d0)
at build/ALPHA_FS/python/swig/event_wrap.cc:4534
#6 0x0000000000446903 in _wrap_simulate (self=0x0, args=0x1c0c4d0)
at build/ALPHA_FS/python/swig/event_wrap.cc:4584
#7 0x00007ffff73fe313 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#8 0x00007ffff73ffd60 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#9 0x00007ffff73fe0ab in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#10 0x00007ffff73fe928 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#11 0x00007ffff73ffd60 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#12 0x00007ffff73ffe32 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0
#13 0x00007ffff73ff0b9 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#14 0x00007ffff73ffd60 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#15 0x00007ffff73fe0ab in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#16 0x00007ffff73ffd60 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#17 0x00007ffff73ffe32 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0
---Type <return> to continue, or q <return> to quit---
#18 0x00007ffff741dd1c in PyRun_StringFlags () from /usr/lib/libpython2.6.so.1.0
#19 0x000000000056414c in m5Main (argc=3, argv=0x7fffffffe2c8)
at build/ALPHA_FS/sim/init.cc:256
#20 0x0000000000409aeb in main (argc=3, argv=0x7fffffffe2c8) at
build/ALPHA_FS/sim/main.cc:57
(gdb)
As you can see
#19 0x000000000056414c in m5Main (argc=3, argv=0x7fffffffe2c8)
at build/ALPHA_FS/sim/init.cc:256
#20 0x0000000000409aeb in main (argc=3, argv=0x7fffffffe2c8) at
build/ALPHA_FS/sim/main.cc:57
So the segmentation fault occurs in main function. I think the
simulation has not been started yet. What does that mean?
From the gdb output, it does not seem to me that a segmentation fault
occurred. gdb stopped the execution when the required number of cycles
got completed.
--
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
