[Top][All Lists]

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

Re: building on macOS?

From: Ben Abbott
Subject: Re: building on macOS?
Date: Wed, 07 Nov 2018 07:37:12 -0800

On Nov 6, 2018, at 3:54 PM, Ben Abbott <address@hidden> wrote:

On Nov 6, 2018, at 15:38, John W. Eaton <address@hidden> wrote:

On 11/06/2018 05:12 PM, Carlo De Falco wrote:
On 6 Nov 2018, at 22:41, Sebastian Schöps <address@hidden> wrote:

Dmitri A. Sergatskov wrote
Running "make V=1" -- finished building w/o problem.
This is on Fedora 29.

I have the same issue on macOS (default branch, with Gui) and "make V=1"
does not help here...
/bin/sh run-octave --norc --silent --no-history --path
/private/tmp/octave-octave-app-20181106-78235-s9u83m/doc/interpreter/ --eval
"interpimages ('doc/interpreter/', 'interpn', 'txt');"
fatal: caught signal Segmentation fault: 11 -- stopping myself...

I completed the bisection search, this seems to be the first bad revision for me :
$ hg bisect -g
The first bad revision is:
changeset:   25994:332be8be16eb
user:        John W. Eaton <address@hidden>
date:        Fri Sep 28 18:18:09 2018 -0400
summary:     dynamically load qt graphics
can someone confirm that a00379f6f8c4 builds correctly while 332be8be16eb fails?

Can someone also run the failing version under gdb or get a core file and run gdb on that and the octave-gui executable and see where the segfault happens?


Apple’s clang supports lldb. run-octave needs to be adjusted to use lldb.

I was looking at this yesterday. I think all the needed translation info is at the link below.



In the lldb debugger, octave exists with 

Process 79077 exited with status = 0 (0x00000000) Terminated due to signal 5

For rev  the attached log results when I run manually.


Attachment: ae9d6a491c06.log
Description: Binary data

reply via email to

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