1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/118/none/786440 b/results/classifier/118/none/786440
new file mode 100644
index 000000000..6ab231b9b
--- /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.]
+