summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/semantic/1701974
blob: 702d3e1cd884f127c47d86a33048691785b90601 (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
semantic: 0.404
instruction: 0.385
device: 0.378
vnc: 0.293
network: 0.247
graphic: 0.227
socket: 0.226
mistranslation: 0.211
other: 0.196
boot: 0.150
KVM: 0.135
assembly: 0.111

pwrite does not work right under qemu-sh4

The pwrite system call has no effect when writing to a non-zero file position, in a program running under qemu-sh4 (version 2.9.0).

How to reproduce:
- Compile the program:
  sh4-linux-gnu-gcc-5 -O -Wall -static -o test-pwrite test-pwrite.c
- Set environment variable for using qemu-sh4 (actually not needed, since the program is statically linked here).
- ~/inst-qemu/2.9.0/bin/qemu-sh4 test-pwrite

Expected output:
buf = 01W3456789

Actual output:
buf = 0123456789
test-pwrite.c:56: assertion 'strcmp ("01W3456789",buf) == 0' failed
qemu: uncaught target signal 6 (Aborted) - core dumped





In case it matters: My host platform is Linux/x86_64.

The behaviour in qemu-2.10 is the same as in qemu-2.9.

This might be related to this fix:

> https://git.qemu.org/?p=qemu.git;a=commit;h=8bf8e9df4a7d82c7a47cc961c9cdee1615595de0

FWIW, if you're interested in sh4, please join #debian-ports on OFTC and subscribe to the debian-superh mailing list. We're doing lots of sh4 development and testing QEMU in Debian.

Works fine in qemu-2.11:
$ ~/inst-qemu/2.11.0/bin/qemu-sh4 test-pwrite
buf = 01W3456789