1 files changed, 64 insertions, 0 deletions
diff --git a/results/classifier/118/none/1548166 b/results/classifier/118/none/1548166
new file mode 100644
index 000000000..b733371a3
--- /dev/null
+++ b/results/classifier/118/none/1548166
@@ -0,0 +1,64 @@
+debug: 0.735
+graphic: 0.711
+x86: 0.707
+device: 0.676
+performance: 0.600
+semantic: 0.539
+architecture: 0.526
+files: 0.499
+ppc: 0.476
+hypervisor: 0.475
+network: 0.458
+socket: 0.456
+peripherals: 0.408
+register: 0.407
+vnc: 0.402
+PID: 0.368
+risc-v: 0.360
+kernel: 0.342
+VMM: 0.336
+mistranslation: 0.331
+permissions: 0.315
+TCG: 0.310
+user-level: 0.300
+virtual: 0.287
+i386: 0.268
+arm: 0.219
+KVM: 0.175
+boot: 0.175
+assembly: 0.147
+
+QEMU crash after send data from Host through serial port 
+
+Hi All
+
+I have two computer, one is Win7 32 another is Win7 64, Both computer meet this issue.
+My QEMU version is qemu-w32-setup-20160215
+
+I want used EDK2 OVMF with Intel UDK Debugger tools to do source level debug
+I had install com0com Virtual Com Port, and set COM3 connect to COM4
+
+Intel UDK Debugger tools used COM3
+QEMU run OVMF used COM4
+
+First execute Intel UDK Debugger tools, then launch QEMU
+C:\Program Files\qemu\qemu-system-x86_64.exe -bios "C:\EDK2\Build\OvmfX64\DEBUG_VS2010\FV\OVMF.fd" -serial COM4
+Then QEMU crashes on stratup
+
+I have do some experiment
+Execute terminal tool Tera Term and used COM3
+launch QEMU and used COM4
+C:\Program Files\qemu\qemu-system-x86_64.exe -bios "C:\EDK2\Build\OvmfX64\DEBUG_VS2010\FV\OVMF.fd" -serial COM4
+This is fine and i can see OVMF trace log on terminal
+But if i press "Down" key on terminal, then QEMU crashe
+It's caused by terminal send data("Down" key) to QEMU
+
+Have somebody can share some information about this?
+
+Thanks a lot.
+Sugar
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+