|
From: | Stefan Brüns |
Subject: | [Octave-bug-tracker] [bug #55395] Java tests messes up the stack limits, causes failure of sparse/bicgstab.m |
Date: | Fri, 4 Jan 2019 22:37:26 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
Follow-up Comment #6, bug #55395 (project octave): This is a genuine Java bug, it also segfaults (typically not visible, as it has a signal handler installed) when running standalone. You can see this when running e.g. $> gdb -q --batch -ex run -ex "bt 6" -ex quit java Thread 2 "java" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff5e80700 (LWP 26318)] 0x00007fffd863d526 in ?? () #0 0x00007fffd863d526 in ?? () #1 0x0000000000000202 in ?? () #2 0x00007fffd863d280 in ?? () #3 0x00007ffff7386374 in Abstract_VM_Version::_vm_major_version () from /usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so #4 0x00007ffff5e7f480 in ?? () #5 0x00007ffff6fd3899 in VM_Version::get_processor_features() () from /usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55395> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |