summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/output/instruction/1724485
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
commitc50b0c4da17b6e83640e4ed2380fffb5f507c846 (patch)
treeb4f203fce1380e2ea3578a784bb8ee060fe42cbd /results/classifier/zero-shot-user-mode/output/instruction/1724485
parent61361f925d4914a6608a0076e64cc2399311ed5f (diff)
downloadqemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.tar.gz
qemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.zip
add zero-shot results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/output/instruction/1724485')
-rw-r--r--results/classifier/zero-shot-user-mode/output/instruction/172448524
1 files changed, 24 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/output/instruction/1724485 b/results/classifier/zero-shot-user-mode/output/instruction/1724485
new file mode 100644
index 000000000..b0f06b5d2
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/output/instruction/1724485
@@ -0,0 +1,24 @@
+instruction: 0.529
+runtime: 0.258
+syscall: 0.213
+
+
+
+Invalid assertion in arm_read_memory_func
+
+Hi,
+
+I think there is an invalid assertion in arm_read_memory_func:
+assert(info->endian == BFD_ENDIAN_LITTLE)
+
+I face it in the following use case: target armeb-linux (I use qemu user mode), -d in_asm -cpu any.
+
+At some point during program startup, glibc's _dl_new_object calls strlen, which is written in thumb2 mode (armv6t2). So print_insn_arm() calls arm_read_memory_func() with length==2, and info->flags == INSN_ARM_BE32, and the assert is false.
+
+If I remove the assert, execution continues OK.
+
+With the assert, I get the error message from the assert, and qemu then stalls.
+
+Can you confirm the assert can be removed? Or if not, explain me how to avoid/fix the subsequent qemu stall?
+
+Thanks
\ No newline at end of file