[Octave-bug-tracker] [bug #53514] Memory leaks in 4.4 release

[Rik]

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

I don't get any print out at all when I have leak_check_at_exit=0.  It just
runs and exits.

I have -O0 and -ggdb3 in my CFLAGS now, but the backtrace for the segfault in
ov-class.cc is still uninformative.


#0  0x00007f52d129f2b4 in  ()
#1  0x49656e696c65746e in  ()
#2  0x02100800000406e3 in  ()
Python Exception <class 'OverflowError'> int too big to convert: 
#3  0xbfebfbff7ffafbbf in  ()#4  0x01c0003f1c004121 in  ()
#5  0x000000000000003f in  ()
#6  0x0000000000000000 in  ()


I think this may have something to do with the Java JDK because I get a
message in gdb about "Installing openjdk unwinder".  Also, "test ov-java.cc"
segfaults in the same way.  I am going to disable java in the build and see
what happens.

    _______________________________________________________

Reply to this item at:

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

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