octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults i


From: Rik
Subject: [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave
Date: Thu, 24 Mar 2016 20:11:06 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Follow-up Comment #35, bug #47372 (project octave):

Good news / Bad news.  First, the good news is that neither of the two patches
fixed the segfault.  This means the nil_rep class variable is probably a red
herring.  In another test, I edited __magic_read__.cc and replaced all static
variables with ordinary ones.  This also did not fix the problem.

>From gdb, the commonality is that all segfaults go through the destructor
octave_dlopen_shlib::~octave_dlopen_shlib (void) which calls 'dlclose
(library)'. 

The bad news is that I don't know where to go from here.  We could remove the
dlclose and simply wait until Octave exits and the OS reaps the memory.  Or we
could assume that it is some interaction between my version of gcc, glibc
(since dlopen/dlclose are used), and GraphicsMagick.

It does segfault reliabliy with the Address Sanitizer turned on which means
there is at least a testbed for ideas, but I don't know what they would be.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]