[Octave-bug-tracker] [bug #58004] [octave forge] (io) xmlread.m makes Octave crash

[John W. Eaton]

Follow-up Comment #30, bug #58004 (project octave):

You could try "make install V=1" and see whether strip is ever called or if
install is given the -s option, but Octave's Makefile shouldn't be set up to
strip by default.

The behavior I observe varies.  I've been able to capture stack traces in
which the call stack of the Octave interpreter thread appears to be completely
invalid.  I'm attaching an example.  The first file is the output of "thread
apply all bt" after starting Octave and executing the commands


usejava ("jvm");
javaaddpath ("/usr/share/java/xercesImpl.jar")
figure ();
line ();
print ('line.svg');


The second is after a segfault happens when running


for i = 1:100000
  parser = javaObject ("org.apache.xerces.parsers.DOMParser");
end


Comparing the stack traces for threads 1-7, they all look about the same
except for thread 6, which gdb can no longer make any sense of.  That's the
one that was running the Octave interpreter.  Maybe I'm chasing the wrong
thing here, but how can we find what is executing when that happens?

(file #49249, file #49250)
    _______________________________________________________

Additional Item Attachment:

File name: stack-after-jvm-init.txt       Size:29 KB
    <https://savannah.gnu.org/file/stack-after-jvm-init.txt?file_id=49249>

File name: stack-after-segfault.txt       Size:30 KB
    <https://savannah.gnu.org/file/stack-after-segfault.txt?file_id=49250>



    _______________________________________________________

Reply to this item at:

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

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