blob: a77eb63a43980108374814bb2e72ecfda4c08d19 (
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
|
graphic: 0.688
semantic: 0.677
mistranslation: 0.673
ppc: 0.635
device: 0.635
performance: 0.592
TCG: 0.585
architecture: 0.585
network: 0.574
vnc: 0.520
debug: 0.517
PID: 0.510
files: 0.473
socket: 0.439
hypervisor: 0.438
kernel: 0.420
x86: 0.395
i386: 0.386
arm: 0.382
boot: 0.372
KVM: 0.354
permissions: 0.348
register: 0.346
VMM: 0.301
user-level: 0.287
peripherals: 0.250
virtual: 0.204
assembly: 0.190
risc-v: 0.157
something wrong in function type_initialize() in object.c in the source code of qemu-1.1.0
In the function type_initialize() in file object.c, about line 237, the sentence :
memset((void *)ti->class + class_size, 0, ti->class_size - class_size);
after the
if (type_has_parent(ti)){}
will clean the information copied from the parent in the if block.
I'm wondering whether this will lead to a bug. Thanks.
That code has been remove with this commit:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=745549c8d0273d3a3d9c3701
... so I think we can close this ticket nowadays.
|