1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/489 b/results/classifier/zero-shot/108/other/489
new file mode 100644
index 000000000..849433e46
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/489
@@ -0,0 +1,52 @@
+debug: 0.899
+graphic: 0.822
+files: 0.813
+semantic: 0.769
+device: 0.717
+other: 0.705
+PID: 0.649
+performance: 0.647
+vnc: 0.601
+permissions: 0.565
+network: 0.497
+socket: 0.494
+boot: 0.456
+KVM: 0.374
+
+Assertion raised when hitting gdb break point in qemu-system-avr
+Description of problem:
+An assertion is triggered when inserting a break point via gdb and continuing from gdb until hitting the break point:
+```
+./qemu-system-avr -nographic -machine uno -s -S -bios simpletest.bin 
+Starting up...
+qemu-system-avr: ../accel/tcg/translate-all.c:1476: tb_gen_code: Assertion `tb->size != 0' failed.
+Aborted (core dumped)
+```
+The matching gdb session:
+```
+~/gdb/gdb-10.1-OK/gdb/avr-gdb 
+GNU gdb (GDB) 10.1
+[snipped copyright notice ]
+(gdb) tar rem :1234
+Remote debugging using :1234
+warning: Target-supplied registers are not supported by the current architecture
+warning: No executable has been specified and target does not support
+determining executable automatically.  Try using the "file" command.
+0x00000000 in ?? ()
+(gdb) b *0xb2
+Breakpoint 1 at 0xb2
+(gdb) c
+Continuing.
+Remote connection closed
+(gdb) 
+```
+Steps to reproduce:
+1. Start qemu with command line given in description above
+2. Connect to qemu session using avr-gdb, also given in description.
+3. From avr-gdb, place a break point somewhere in code, then continue
+4. When qemu reaches break point, an assertion is raised
+Additional information:
+1. When running without a break point there is no assertion
+2. Problem appears to be triggered only when inserted break point is hit.
+3. Stepping in gdb works
+4. This problem isn't evident in qemu 6.0.0