Я пытаюсь настроить KGDB + QEMU в системе arm64, все в порядке, пока точки останова, хост gdb, кажется, никогда не попадет в ядро, работающее на виртуальной машине.
HOST
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/vm/q2/kgdb/vmlinux...done.
(gdb) set remotebaud 115200
(gdb) target remote /dev/pts/3
Remote debugging using /dev/pts/3
Ignoring packet error, continuing...
Remote 'g' packet reply is of odd length: 00b06012008ffff10000000000000bd0120080ff20bd60120080ffff010100000000000001000000000000002b485e120080ffff17000000000000001001000000000001860d2110080ffff602d34120080ffffffe0f50500000000002036120080ffff353a8c120080ffff273a8c20080fff082934120080ffff0000000000000000000000000000fffffffffffffff002034120080ffff002036120080ffff670000000000000018d436120080ffff000000000000000007000000000000000000000000000000001051120080ffff0000000000000000008e827c0000ffffc03c8c120080ffff74ad1d100080ffffc03c8c120080ffffdcac1d10080ffff05000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
(gdb) b wake_up_process
Breakpoint 1 at 0xffff80001012f924: wake_up_process. (2 locations)
(gdb) c
The program is not being run.
(gdb) b start_kernel
Breakpoint 2 at 0xffff800011b10c98: file /home/kernel/init/main.c, line 576.
(gdb) c
The program is not being run.
(gdb) l
11
12 #define MODULE_PARAMETER_DEF(xxx)\
13 static int xxx##_set(const char *val, const struct kernel_param *kp)\
14 {\
15 u32 n;\
16 int ret;\
17 if (atomic_read(&test_status))\
18 return -EBUSY;\
19 ret = kstrtou32(val, 10, &n);\
20 if (ret != 0)\
Виртуальный
estuary:/$ echo g > /proc/sysrq-trigger
[ 48.700583] sysrq: DEBUG
Entering kdb (current=0xffff00007c828e00, pid 184) on processor 0 due to Keyboard Entry
[0]kdb> kgdb
Entering please attach debugger or use $D#44+ or $3#33
aK#00080ff0020800000040000000000000000000000000000000000000000000000000000000000000#0b80020000080000000000000000000000000000000000000000000000000000000000000000000000000000000000006ff09f0000f040000000000000000000000000000000000000000000000000000000000000b$00b060120080ffff010000000000000000bd60120080ffff20bd60120080ffff010100000000000001000000000000002b485e120080ffff170000000000000010010000000000001860d2110080ffff602d34120080ffffffe0f50500000000002036120080ffff353a8c120080ffff273a8c920080ffff082934120080ffff00000000000000000000000000000000ffffffffffffffff002034120080ffff002036120080ffff670000000000000018d436120080ffff000000000000000007000000000000000000000000000000001051120080ffff0000000000000000008e827c0000ffffc03c8c120080ffff74ad1d100080ffffc03c8c120080ffffdcac1d100080ffff0500406000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000#be
Не знаете, в чем причина вышеуказанной проблемы, как заставить continue работать?