Hi,

I am trying to use remote gdb for debugging some kernel panics, but I have
some issues. The ports are as follows :
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001
0: system.remote_gdb.listener: listening for remote gdb #2 on port 7002
0: system.remote_gdb.listener: listening for remote gdb #3 on port 7003

So I do the following when I attach the remote gdb
(gdb) set remote Z-packet on
(gdb)  target remote localhost:7001
Remote debugging using localhost:7001
0xfffffc0000010130 in ?? ()
(gdb) c
Continuing.


In the output from gem5, it shows up:
3390763292000: system.cpu1.break_event: break event panic triggered
panic: Halt not implemented!
 @ cycle 3390766025750
[halt:build/ALPHA/cpu/o3/cpu.hh, line 469]
Memory Usage: 1255796 KBytes
Program aborted at cycle 3390766025750
./fw_thrd.sh: line 3: 13915 Aborted                 ../build/ALPHA/gem5.opt
-d ../output_2/firewall_equ_thrd_$num --debug-flags=Trace
../configs/example/fs.py --cpu-type=detailed --caches --l2cache -b
firewall_thrd -f /tmp/pritha/equinox_trace_1000000 -o
/tmp/pritha/firewall_op_thrd_$num -z $num --kernel vmlinux_firewall -n 4

But on the gdb, it does not give control. The panic is on cpu1, to which I
had attached the gdb.  The gdb exits directly.. Shouldn't it give control
to user before the simulation panics and stops? Is there some step I am
missing?

(gdb) c
Continuing.

Watchdog has expired.  Target detached.

(gdb)
The program is not being run.
(gdb) bt
No stack.

Thanks,
Pritha
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to