summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2/output/debug/1552
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2/output/debug/1552')
-rw-r--r--results/classifier/deepseek-2/output/debug/155216
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/output/debug/1552 b/results/classifier/deepseek-2/output/debug/1552
new file mode 100644
index 000000000..9ece41d8f
--- /dev/null
+++ b/results/classifier/deepseek-2/output/debug/1552
@@ -0,0 +1,16 @@
+
+newer version(>=5.2.0) of qemu-system-aarch64 cannot debug arm64 linux kernel
+Description of problem:
+
+Steps to reproduce:
+1. Run QEMU in on teminal.
+2. Run gdb-multiarch in another terminal, for example: gdb-multiarch ./linux-5.10.4/vmlinux
+3. In gdb-multiarch, enter three commands in sequence:"target remote localhost:1234"、"b do_sys_open"、"continue"
+4. GDB breakpoint cannot take effect
+5. If using qemu-system-aarch64 5.0.0(manually compiled),GDB breakpoint can take effect.
+Additional information:
+I tested this problem using different combinations:  
+Host Os:Ubuntu18/Ubuntu20/Ubuntu22  
+ARM64 Linux Kernel: 5.4.50/5.10.4  
+QEMU:qemu 2.11/qemu 4.2/qemu 5.0/qemu 5.2/qemu 6.2/qemu 7  
+Finally, I found out that arm64 linux kernel cannot be debugged since qemu-system-aarch64 5.2.0.