Re: Memory leaks in Octave

[Rik]

On 09/15/2017 09:00 AM, address@hidden wrote:

Subject:

Re: Memory leaks in Octave

From:

siko1056 <address@hidden>

Date:

09/15/2017 05:55 AM

To:

address@hidden

List-Post:

<mailto:address@hidden>

Content-Transfer-Encoding:

quoted-printable

Precedence:

list

MIME-Version:

1.0

References:

<address@hidden> <address@hidden> <address@hidden>

In-Reply-To:

<address@hidden>

Message-ID:

<address@hidden>

Content-Type:

text/plain; charset=UTF-8

Message:

3

Rik-4 wrote

Dmitri A. Sergatskov wrote

​My builds with gcc7.1.1 and ASAN pretty much fail 

I'm building with gcc-5.4.0 and I don't see this. 

My experience using "gcc-7 (SUSE Linux) 7.1.1 20170607" was also bad.  Lots
of linking errors, when the oct-files were created.  But using "gcc (SUSE
Linux) 4.8.5" works for me.  The first issue "make check" detected is QT5
related:

 libinterp/octave-value/ov-class.cc-tst ......................ASAN:SIGSEGV
=================================================================
==4516== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc
0x7fae70a6e2b4 sp 0x7faec2abf398 bp 0x7fae8aa78820 T10)
AddressSanitizer can not provide additional info.
    #0 0x7fae70a6e2b3 (+0x2b3)
Thread T10 (QThread) created by T0 here:
    #0 0x7faefcdf213b (/usr/lib64/libasan.so.0.0.0+0xb13b)
    #1 0x7faef8890fd5 (/usr/lib64/libQt5Core.so.5.6.2+0xaefd5)
==4516== ABORTING

Did I trapped into inappropriate threading options?

Did you build with '-g'?  That is a really short backtrace that doesn't give much information about where the problem might lie.  The backtraces that I have been getting are more like a page long.  In fact, I have been building with '-ggdb3 -O0' so that as little optimization as possible that might remove intermediate variables of interest is performed.

--Rik