summary refs log tree commit diff stats
path: root/results/classifier/118/debug/489
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/debug/489')
-rw-r--r--results/classifier/118/debug/48967
1 files changed, 0 insertions, 67 deletions
diff --git a/results/classifier/118/debug/489 b/results/classifier/118/debug/489
deleted file mode 100644
index f4d1e912..00000000
--- a/results/classifier/118/debug/489
+++ /dev/null
@@ -1,67 +0,0 @@
-debug: 0.899
-architecture: 0.893
-graphic: 0.822
-files: 0.813
-TCG: 0.806
-semantic: 0.769
-device: 0.717
-mistranslation: 0.664
-hypervisor: 0.655
-PID: 0.649
-performance: 0.647
-register: 0.642
-vnc: 0.601
-user-level: 0.578
-permissions: 0.565
-risc-v: 0.546
-i386: 0.522
-ppc: 0.511
-network: 0.497
-socket: 0.494
-x86: 0.462
-VMM: 0.459
-boot: 0.456
-peripherals: 0.452
-virtual: 0.444
-KVM: 0.374
-arm: 0.372
-kernel: 0.296
-assembly: 0.211
-
-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