[Octave-bug-tracker] [bug #55395] Java tests messes up the stack limits, causes failure of sparse/bicgstab.m

[Stefan Brüns]

Follow-up Comment #10, bug #55395 (project octave):

@mtmiller - which version of octave are you running?

If your JVM does not insert a stack guard page for the main (Java calls in
primordial) thread, there must be a difference.

The relevant code likely is here:
https://github.com/JetBrains/jdk8u_hotspot/commit/8302c38e12be9a7e0259c81b6ca426cd7f79f53d#diff-852a551ce56c81e8f2f0770135243c14

Can you set a breakpoint on 'JavaThread::create_stack_guard_pages()', and see
if there are any differences:


(gdb) bt 7
#0  0x00007fffe71dec42 in JavaThread::create_stack_guard_pages() () from
/usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so
#1  0x00007fffe71df063 in Threads::create_vm(JavaVMInitArgs*, bool*) () from
/usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so
#2  0x00007fffe6d88492 in JNI_CreateJavaVM () from
/usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so
#3  0x00007ffff74f96c8 in ?? () from
/usr/lib64/octave/4.4.1/liboctinterp.so.6
#4  0x00007ffff74f9e05 in ?? () from
/usr/lib64/octave/4.4.1/liboctinterp.so.6
#5  0x00007ffff74fa1be in FjavaMethod(octave_value_list const&, int) () from
/usr/lib64/octave/4.4.1/liboctinterp.so.6
#6  0x00007ffff7458f08 in octave_builtin::call(octave::tree_evaluator&, int,
octave_value_list const&) () from /usr/lib64/octave/4.4.1/liboctinterp.so.6
(More stack frames follow...)
(gdb) info threads
  Id   Target Id                                      Frame
* 1    Thread 0x7fffef84aa00 (LWP 17550) "octave-cli" 0x00007fffe71dec42 in
JavaThread::create_stack_guard_pages() () from
/usr/lib64/jvm/java-11-openjdk-11/lib/server/libjvm.so
  2    Thread 0x7fffef829700 (LWP 17551) "octave-cli" 0x00007ffff42614dc in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  3    Thread 0x7fffef028700 (LWP 17552) "octave-cli" 0x00007ffff42614dc in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  4    Thread 0x7fffea827700 (LWP 17553) "octave-cli" 0x00007ffff42614dc in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  5    Thread 0x7fffe7eac700 (LWP 17554) "octave-cli" 0x00007ffff57c2e2c in
sigtimedwait () from /lib64/libc.so.6
(gdb) p/x $rsp
$5 = 0x7fffffffb9b0

 
maps:

7ffff7ffe000-7ffff7fff000 rw-p 00000000 00:00 0 
7fffff805000-7ffffffff000 rw-p 00000000 00:00 0                         
[stack]


The JVM is obviously created from the main thread.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55395>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/