blob: 2c58398a934ab75fddaed62e013b23ecc8707d07 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
virtual: 0.877
device: 0.716
debug: 0.666
graphic: 0.665
x86: 0.664
arm: 0.564
ppc: 0.559
semantic: 0.553
mistranslation: 0.533
socket: 0.530
kernel: 0.500
network: 0.499
vnc: 0.499
risc-v: 0.489
user-level: 0.445
VMM: 0.441
permissions: 0.441
boot: 0.428
i386: 0.408
PID: 0.394
performance: 0.394
architecture: 0.388
register: 0.381
hypervisor: 0.286
TCG: 0.283
KVM: 0.232
files: 0.212
peripherals: 0.154
assembly: 0.152
qemu core dumps with -serial mon:vc
qemu 1.5.2-1 dumps core when asked to put the monitor on a virtual console. For example, suppose you want to monitor the second serial port, you might try something like:
qemu-system-x86_64 -serial null -serial mon:vc
But that creates a core dump. In fact, even re-creating what should be the default dumps core:
$ qemu-system-x86_64 -serial mon:vc:80Cx25C
Segmentation fault (core dumped)
I'm not including a backtrace because the bug is so easy to reproduce, but I can provide more info if necessary.
Hi,
This problem has been solved by
commit 7b7ab18d0b9769b5f39e663fa55caed461b1202e:
Author: Michael Roth <email address hidden>
Date: Tue Jul 30 13:04:22 2013 -0500
chardev: fix CHR_EVENT_OPENED events for mux chardevs
Patch link:
http://patchwork.ozlabs.org/patch/263458/
|