blob: a799e40a82401038162970b310b276750d43ef1b (
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
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
x86: 0.878
architecture: 0.855
debug: 0.838
user-level: 0.822
device: 0.770
boot: 0.760
graphic: 0.737
semantic: 0.731
arm: 0.673
performance: 0.649
ppc: 0.601
register: 0.578
socket: 0.491
permissions: 0.446
kernel: 0.390
VMM: 0.380
PID: 0.380
network: 0.348
hypervisor: 0.339
risc-v: 0.307
files: 0.296
vnc: 0.282
peripherals: 0.264
virtual: 0.227
mistranslation: 0.219
assembly: 0.146
TCG: 0.116
i386: 0.102
KVM: 0.029
--------------------
debug: 0.969
arm: 0.942
user-level: 0.882
virtual: 0.777
network: 0.673
TCG: 0.031
files: 0.024
hypervisor: 0.014
x86: 0.012
performance: 0.010
register: 0.009
socket: 0.008
PID: 0.006
risc-v: 0.005
architecture: 0.005
boot: 0.003
device: 0.003
kernel: 0.002
vnc: 0.002
i386: 0.002
semantic: 0.002
ppc: 0.002
VMM: 0.001
assembly: 0.001
graphic: 0.001
peripherals: 0.001
permissions: 0.001
KVM: 0.000
mistranslation: 0.000
Regression: SIGSEGV running Java
I have a build script that bootstraps a Debian armhf image. Part of the process involves running a Java program while inside a chroot. I am using Debian's qemu-user-static package to run the armhf Java binary on an amd64 system.
qemu-user-static version 1:2.7+dfsg-3~bpo8+2 works fine. Version 1:2.8+dfsg-1~bpo8+1 always causes Java to crash with a SIGSEGV. The location of the crash appears to be random and hasn't been the same twice.
I am using the Azul Systems Zulu Embedded Java runtime, rather than the regular OpenJDK runtime, because the Zulu runtime has an arm32 JIT whereas OpenJDK is interpreter-only on arm32.
I can reproduce the problem easily by mounting the image created by my build script and executing "java -XshowSettings -version" in a chroot. I can give you the image if that would help debug the problem.
Additional investigation reveals the problem has something to do with the Azul ARM32 JIT. If I run Java with -Xint to force interpreter-only mode, this problem doesn't occur.
Similar issue reported in two other places on the net:
https://github.com/multiarch/qemu-user-static/issues/18 "qemu-arm-static 2.8 and Java+Maven setup not working"
https://bugs.linaro.org/show_bug.cgi?id=3259#c4 Bug 3259 - Javac fails within qemu-aarch64-static chroot on x86
fyi, similar seen for Raspbian9:
https://bugs.launchpad.net/raspbian/+bug/1732556
Hi -- I believe we fixed the Java crashes as part of work done for the 2.12 release (and perhaps 3.0, I forget). Does this still reproduce with the most recent release of QEMU (eg the 4.0 release candidate) ?
[Expired for QEMU because there has been no activity for 60 days.]
|