3 files changed, 144 insertions, 0 deletions
diff --git a/results/classifier/118/none/786 b/results/classifier/118/none/786
new file mode 100644
index 00000000..7a0eb50e
--- /dev/null
+++ b/results/classifier/118/none/786
@@ -0,0 +1,47 @@
+boot: 0.769
+files: 0.692
+device: 0.611
+graphic: 0.459
+kernel: 0.367
+semantic: 0.326
+i386: 0.281
+arm: 0.280
+network: 0.273
+hypervisor: 0.263
+ppc: 0.262
+socket: 0.226
+vnc: 0.221
+x86: 0.213
+mistranslation: 0.198
+user-level: 0.170
+architecture: 0.160
+debug: 0.143
+risc-v: 0.120
+PID: 0.110
+TCG: 0.107
+VMM: 0.105
+virtual: 0.104
+peripherals: 0.099
+KVM: 0.099
+register: 0.085
+performance: 0.070
+permissions: 0.069
+assembly: 0.058
+
+assert in qemu-6.2.0/hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen)
+Description of problem:
+assert and crash when -acpitable argument is used. Specifically, the argument was "-acpitable file=my_file.bin" which causes the assert and crash. 
+
+The other arguments, I hope, are not critical. In brief, I'm using secure boot (with ovmf_code.secboot.fd), and a sw tpm as well. But hopefully these are not relevant.
+
+The assert with -acpitable is a regression since it worked with version 6.1.0
+
+The actual error message in qemu 6.2.0 is
+
+qemu-6.2.0/hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen)
+Steps to reproduce:
+1.
+2.
+3.
+Additional information:
+
diff --git a/results/classifier/118/none/786440 b/results/classifier/118/none/786440
new file mode 100644
index 00000000..6ab231b9
--- /dev/null
+++ b/results/classifier/118/none/786440
@@ -0,0 +1,57 @@
+performance: 0.672
+device: 0.642
+semantic: 0.631
+graphic: 0.625
+hypervisor: 0.624
+architecture: 0.580
+mistranslation: 0.575
+user-level: 0.538
+virtual: 0.495
+debug: 0.478
+network: 0.442
+i386: 0.428
+socket: 0.380
+permissions: 0.361
+x86: 0.340
+kernel: 0.337
+peripherals: 0.325
+register: 0.312
+ppc: 0.258
+assembly: 0.244
+PID: 0.234
+vnc: 0.201
+boot: 0.169
+risc-v: 0.161
+VMM: 0.155
+files: 0.153
+arm: 0.137
+TCG: 0.126
+KVM: 0.119
+
+qcow2 double free
+
+version 0.14.1 when using qcow2 images, after some time, glibc detects a double free or corruption.
+
+On Sun, May 22, 2011 at 8:58 AM, Andrew Kroll <email address hidden> wrote:
+> Public bug reported:
+>
+> version 0.14.1 when using qcow2 images, after some time, glibc detects a
+> double free or corruption.
+
+Any specific information on what the guest was doing?  Was it doing
+heavy I/O or was it idle?
+
+Are you using IDE emulation or virtio-blk?
+
+Please provide a backtrace:
+1. Build with ./configure --disable-strip (or use matching -debuginfo
+packages from your distro)
+2. Run with gdb --args path/to/qemu [...args...]
+
+When the abort happens please use the "bt" GDB command to display a backtrace.
+
+Stefan
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/none/786442 b/results/classifier/118/none/786442
new file mode 100644
index 00000000..e1d0ef62
--- /dev/null
+++ b/results/classifier/118/none/786442
@@ -0,0 +1,40 @@
+architecture: 0.782
+device: 0.768
+semantic: 0.708
+kernel: 0.668
+network: 0.667
+socket: 0.658
+risc-v: 0.642
+TCG: 0.622
+ppc: 0.617
+debug: 0.612
+vnc: 0.604
+VMM: 0.574
+register: 0.569
+files: 0.560
+hypervisor: 0.550
+PID: 0.549
+permissions: 0.537
+boot: 0.505
+i386: 0.486
+x86: 0.484
+performance: 0.476
+graphic: 0.448
+user-level: 0.425
+mistranslation: 0.417
+arm: 0.398
+peripherals: 0.387
+KVM: 0.342
+virtual: 0.325
+assembly: 0.246
+
+GCC -O2 causes segfaults
+
+unless compiled without optimizations, no system may be ran except the default with -kvm-enabled
+I had to modify config-host.mak and remove -O2 from CFLAGS to be able to work without kvm.
+
+GCC 4.4.4 qemu-0.14.1
+***NOTE: this has been an issue for several versions.
+
+Sorry, that there were no reactions to this ticket when you've opened it. Since both, GCC 4.4 and QEMU 0.14 are quite outdated nowadays, and AFAIK nobody complains about this issue with newer versions anymore, I think we can close this bug nowadays. If you still have this problem with the latest version of QEMU, please feel free to open this ticket again. 
+