* [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java
@ 2017-01-27 17:18 Rich DiCroce
2017-02-01 22:17 ` [Qemu-devel] [Bug 1659901] " Rich DiCroce
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: Rich DiCroce @ 2017-01-27 17:18 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] [Bug 1659901] Re: Regression: SIGSEGV running Java
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
@ 2017-02-01 22:17 ` Rich DiCroce
2017-10-11 3:36 ` Edward Vielmetti
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Rich DiCroce @ 2017-02-01 22:17 UTC (permalink / raw)
To: qemu-devel
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.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] [Bug 1659901] Re: Regression: SIGSEGV running Java
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
2017-02-01 22:17 ` [Qemu-devel] [Bug 1659901] " Rich DiCroce
@ 2017-10-11 3:36 ` Edward Vielmetti
2017-11-15 22:58 ` pgnet
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Edward Vielmetti @ 2017-10-11 3:36 UTC (permalink / raw)
To: qemu-devel
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
** Bug watch added: github.com/multiarch/qemu-user-static/issues #18
https://github.com/multiarch/qemu-user-static/issues/18
** Bug watch added: Linaro Bug Tracking System #3259
https://bugs.linaro.org/show_bug.cgi?id=3259
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Qemu-devel] [Bug 1659901] Re: Regression: SIGSEGV running Java
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
2017-02-01 22:17 ` [Qemu-devel] [Bug 1659901] " Rich DiCroce
2017-10-11 3:36 ` Edward Vielmetti
@ 2017-11-15 22:58 ` pgnet
2020-01-23 6:05 ` Thomas Huth
2020-03-24 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 6+ messages in thread
From: pgnet @ 2017-11-15 22:58 UTC (permalink / raw)
To: qemu-devel
fyi, similar seen for Raspbian9:
https://bugs.launchpad.net/raspbian/+bug/1732556
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1659901] Re: Regression: SIGSEGV running Java
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
` (2 preceding siblings ...)
2017-11-15 22:58 ` pgnet
@ 2020-01-23 6:05 ` Thomas Huth
2020-03-24 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2020-01-23 6:05 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: New => Incomplete
** Bug watch removed: Linaro Bug Tracking System #3259
https://bugs.linaro.org/show_bug.cgi?id=3259
** Bug watch removed: github.com/multiarch/qemu-user-static/issues #18
https://github.com/multiarch/qemu-user-static/issues/18
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
Incomplete
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1659901] Re: Regression: SIGSEGV running Java
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
` (3 preceding siblings ...)
2020-01-23 6:05 ` Thomas Huth
@ 2020-03-24 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 6+ messages in thread
From: Launchpad Bug Tracker @ 2020-03-24 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
Expired
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659901/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-03-24 4:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-27 17:18 [Qemu-devel] [Bug 1659901] [NEW] Regression: SIGSEGV running Java Rich DiCroce
2017-02-01 22:17 ` [Qemu-devel] [Bug 1659901] " Rich DiCroce
2017-10-11 3:36 ` Edward Vielmetti
2017-11-15 22:58 ` pgnet
2020-01-23 6:05 ` Thomas Huth
2020-03-24 4:17 ` Launchpad Bug Tracker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).