[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]

[Rik]

Update of bug #53733 (project octave):

                 Release:                   4.2.2 => 4.3.91                 

    _______________________________________________________

Follow-up Comment #6:

Under gdb I can confirm a SEGFAULT.  I used


./run-octave -f


and then attached to the running process with 'gdb -p XXXX'.  Within Octave, I
ran


javaaddpath ('.')


Note, I didn't even need to call javaObject.

The backtrace is pretty useless



Installing openjdk unwinder

Thread 4 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ff269261700 (LWP 24191)]
0x00007ff24d0002b4 in ?? ()
(gdb) bt
#0  0x00007ff24d0002b4 in  ()
#1  0x49656e696c65746e in  ()
#2  0x01100800000406e3 in  ()
Python Exception <class 'OverflowError'> int too big to convert: 
#3  0xbfebfbff7ffafbbf in  ()#4  0x01c0003f1c004121 in  ()
#5  0x000000000000003f in  ()
#6  0x0000000000000000 in  ()


This was with the release candidate 4.3.91.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53733>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/