summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/instruction/2590
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:15 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:28 +0200
commit5aa276efcbd67f4300ca1a7f809c6e00aadb03da (patch)
tree9b8f0e074014cda8d42f5a97a95bc25082d8b764 /results/classifier/zero-shot-user-mode/instruction/2590
parent1a3c4faf4e0a25ed0b86e8739d5319a634cb9112 (diff)
downloadqemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.tar.gz
qemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/instruction/2590')
-rw-r--r--results/classifier/zero-shot-user-mode/instruction/259029
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/instruction/2590 b/results/classifier/zero-shot-user-mode/instruction/2590
new file mode 100644
index 000000000..52a1c973c
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/instruction/2590
@@ -0,0 +1,29 @@
+instruction: 0.664
+runtime: 0.228
+syscall: 0.108
+
+
+
+qemu-x86_64: gdb doesn't read symbols from dynamically linked shared libraries.
+Description of problem:
+GDB fails to load dynamically linked shared libraries when connecting to qemu-x86_64, causing it to not recognize symbols from the shared libraries. As a result, breakpoints in shared library functions (e.g, `break printf`) do not work.
+Steps to reproduce:
+1. Start the debug server: `./qemu-x86_64 -g PORT ./x86_64-binary`
+2. Connect GDB to the debug server:
+```
+$ gdb-multiarch ./x86_64-binary
+(gdb) set verbose on
+(gdb) target remote :PORT
+```
+3. GDB displays a warning and fails to load shared libraries:
+```
+(gdb) target remote :PORT
+Remote debugging using :PORT
+warning: platform-specific solib_create_inferior_hook did not load initial shared libraries.
+(gdb) info sharedlibrary
+No shared libraries loaded at this time.
+```
+Additional information:
+This issue does not occur when using gdbserver on a native x86_64 machine and connecting to it from gdb-multiarch on an ARM64 machine, indicating the issue is likely related to QEMU rather than GDB. 
+
+GDB correctly recognizes symbols from the target binary (e.g., the `main` function), and breakpoints at these symbols function as expected.