[Octave-bug-tracker] [bug #63971] Invoking Octave's Java subsystem crashes Octave

[Philip Nienhuis]

Follow-up Comment #24, bug #63971 (group octave):

Thanks Dmitri.

Interpretation of the user reports below shows that Octave itself runs fine
until the Java subsystem gets accessed (i.e., Octave attaches to a JVM), and
then it crashes.

What the superuser.com article that you refer to describes about dll search
paths, sounds like it could well be implemented and set as an optional
security policy. I.e., more or less what I wrote in comment #22.
BTW my Windows 10 and 11 systems are fully up-to-date so should/could have
such restricted dll search options OOTB. Yet I don't see any of that, so I
think it's all due to local settings by company IT departments.

That said, maybe the code that Octave uses to attach to or initialize a JVM
isn't sufficiently robust to gracefully catch unexpected JVM initialization
issues. However I'm insufficiently proficient in C++ and Java stuff to
appreciate the relevant stanzas in ov-java.cc and ov-java.h.



    _______________________________________________________

Reply to this item at:

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

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