blob: 165d72ebc151013b863811b1a68c1819e0346e08 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, I need to classify this bug report into one of the given categories. Let me read through it carefully.
The issue is about QEMU's Windows COM port setup dialog always being invoked and failing if no COM port is available or specified. The user mentions that `CommConfigDialog()` is called in `chardev/char-win.c`, which leads to problems because not all COM ports support this function, causing failures.
Looking at the steps to reproduce, it seems like QEMU doesn't recognize extended COM port specs, making it difficult to test without a specific setup. The user provided a patch that sets default settings instead of using the dialog, which avoids the issue.
Now, considering the categories: Mistranslation is about incorrect semantic mappings in user-mode assembly. Assembly lowering refers to converting high-level code to assembly. Other includes things not fitting elsewhere.
The problem here isn't related to translation or assembly; it's more about how QEMU interacts with Windows COM ports and dialog configurations. It falls under device-related issues because it's dealing with serial port hardware emulation in QEMU, which is a peripheral device.
So, the category should be 'device'.
</think>
device
|