1 files changed, 40 insertions, 0 deletions
diff --git a/results/classifier/118/none/840 b/results/classifier/118/none/840
new file mode 100644
index 000000000..132b32df6
--- /dev/null
+++ b/results/classifier/118/none/840
@@ -0,0 +1,40 @@
+device: 0.681
+graphic: 0.655
+performance: 0.473
+semantic: 0.453
+architecture: 0.412
+files: 0.408
+permissions: 0.395
+register: 0.381
+boot: 0.367
+vnc: 0.351
+peripherals: 0.314
+arm: 0.298
+PID: 0.297
+risc-v: 0.280
+ppc: 0.133
+TCG: 0.115
+user-level: 0.099
+socket: 0.075
+network: 0.066
+VMM: 0.065
+mistranslation: 0.046
+virtual: 0.029
+i386: 0.027
+assembly: 0.015
+debug: 0.014
+kernel: 0.009
+hypervisor: 0.006
+x86: 0.003
+KVM: 0.002
+
+When O2 level is enabled raspi3b board crash randomly when creating abuffer of a differnt size
+Description of problem:
+Sometimes when running the code creating a framebuffer different from the default size ej:1024x768 qemu hangs and crash with a SIGV, making a weird screen that's painted with the original size and the background of the current window merged onto a large window. This happens when you resize a window without updating it's contents, so qemu is crashing before the first frame after reising the window.
+Steps to reproduce:
+1. Create a producedure similar to the one descrived below
+2. Run qemu with O2 enabled(debuggind disabled)
+3. You may need to run it multiple times to see the bug(like two or three times)
+Additional information:
+Here is the example procedure implemented on rust, the mailbox interface is test and it's sure that the procedure it's well implemented:
+[code.rs](/uploads/a28fe33a856fb843d80ffeb078bc6729/code.rs)