[Octave-bug-tracker] [bug #64864] Segfault after 'cd /path/to/somewhere' under Debian

[Petter]

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

I read up a bit and it seems like the problem is that the jvm is attached to
the "primordial thread" (the original thread), which the jvm have a hard time
finding the end of the stack in, to put its stack protection pages.

Using octave-cli:
> __init_java__; test eigs;

Segfaults, since the C stack goes into the jvm stack protection pages.

> test eigs; __init_java__; test eigs;

Does not segfault, since the protection pages are placed with an offset to the
maximum extent of the C stack.

The reason octave-cli has this problem and not octave, is due to octave
spawning a thread.

So I made a patch in which a thread is spawned in main() for the cli
executable, which seems to solve the issue.

I also had a issue with openblas running (apart from the Java problem)

echo "pkg load ltfat; load vars;g = double(g);
G=frsynmatrix(frame('dgt',g,a,M),length(g)); disp (a); (G*G')^(1/2); disp
('done')" | ./octave-cli


It was probably due to https://github.com/OpenMathLib/OpenBLAS/issues/3740 and
a apt-get upgrade solved that for me.

Without the patch there is a segfault still.


(file #55331)

    _______________________________________________________

Additional Item Attachment:

File name: 32682.patch                    Size:1 KB
    <https://file.savannah.gnu.org/file/32682.patch?file_id=55331>



    _______________________________________________________

Reply to this item at:

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

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