diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/deepseek-2/output/debug/1552 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/deepseek-2/output/debug/1552')
| -rw-r--r-- | results/classifier/deepseek-2/output/debug/1552 | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/results/classifier/deepseek-2/output/debug/1552 b/results/classifier/deepseek-2/output/debug/1552 deleted file mode 100644 index 9ece41d8..00000000 --- a/results/classifier/deepseek-2/output/debug/1552 +++ /dev/null @@ -1,16 +0,0 @@ - -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. |