summaryrefslogtreecommitdiffstats
path: root/results/classifier/zero-shot/118/graphic/1555452
blob: 36549c5c660fa56e6942b2065863c6bf3a584d52 (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
graphic: 0.878
mistranslation: 0.724
socket: 0.723
network: 0.715
device: 0.706
debug: 0.676
semantic: 0.658
performance: 0.620
architecture: 0.617
user-level: 0.613
PID: 0.590
files: 0.552
register: 0.523
i386: 0.501
ppc: 0.500
permissions: 0.493
assembly: 0.476
virtual: 0.475
risc-v: 0.466
vnc: 0.449
VMM: 0.439
arm: 0.415
TCG: 0.408
hypervisor: 0.397
peripherals: 0.382
kernel: 0.371
KVM: 0.321
boot: 0.304
x86: 0.155

GDB server does not work in Windows

I build qemu with msys2, MINGW64. After fix the socket_error() problem, and manually specify to use IPv4, GDB server still does not work.  The related qemu command is
"-monitor none -nographic -gdb tcp::1234 -S"
GDB reports "Timed out"

There's a message at https://<email address hidden>/msg357981.html.
I've fixed the socket_error() problem.
I see that qio_channel_create_socket_watch is called.

It seems that someone is fixing this at https://<email address hidden>/msg358825.html

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.

[Expired for QEMU because there has been no activity for 60 days.]