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

[Stefan Brüns]

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

Ok, dug a little bit deeper ...

Apparently, the JVM installs a *temporary* protection page during
initalization. Now, when probing for CPU features, it gets a SEGFAULT - see
https://savannah.gnu.org/bugs/?func=detailitem&item_id=52061#comment19 , and
fails to remove the protection page in its fault handler.

As a side effect, the JVM stack size detection later fails, and the stack size
stays wrong.

This is on a Haswell here.

flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb
invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm
ida arat pln pts flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf


    _______________________________________________________

Reply to this item at:

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

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