Re: Segmentation violation after runtests on Windows

[Rik]

On 03/28/2016 12:33 AM, address@hidden wrote:

Subject:

Re: octave-4.0.1 64 bit binary for windows is uploaded

From:

Tatsuro MATSUOKA <address@hidden>

Date:

03/27/2016 10:36 PM

To:

address@hidden, Arazi Nitzan <address@hidden>, "address@hidden" <address@hidden>, "address@hidden" <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> <address@hidden>

In-Reply-To:

<address@hidden>

Reply-To:

Tatsuro MATSUOKA <address@hidden>

Message-ID:

<address@hidden>

Content-Type:

text/plain; charset=iso-8859-1

Message:

5

> From: Tatsuro MATSUOKA 

> To: tmacchant Arazi Nitzan  "address@hidden" ; "john.david.donoghue
> Cc: 
> Date: 2016/3/27, Sun 17:30
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
> 
> I have confirmed that build_packages.m worked successfully on the PC at my home
> using 64 bit binary that I have buit.
> (Windows 10 Home 64 bit upgraded from windows 7 home 64 bit)
> 
> 
> But I have not tested each packages yet.

I have executed runtests on the mxe-octave 4.0.1 64 bit.
I have found two issues.


I have filed the both

1. bug #47554 : logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue)
2. bug #47555: Segmentation violation after "runtests" mxe-octave 64bit

Tatsuro,

Bug #47555 is a duplicate of bug #41699.  To verify you can run the simplified test procedure

test imread
exit

which should segfault.

The problem seems to be the GraphicsMagick library.  It's possible that Octave is somehow using the library incorrectly, but it seems more likely that the library is to blame.

--Rik