[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: segfault when embedding the interpreter
From: |
c. |
Subject: |
Re: segfault when embedding the interpreter |
Date: |
Sat, 12 Oct 2013 16:48:52 +0200 |
On 12 Oct 2013, at 15:25, John W. Eaton <address@hidden> wrote:
> First, are you sure you are linking with the correct libraries? Is it
> possible that when you run the program it is being linked with some
> older set of libraries? If I do that, I get a segfault.
I think I'm linking the correct libraries:
$ which mkoctfile
/opt/octave/current/bin/mkoctfile
$ LD_LIBRARY_PATH=/opt/octave/current/lib/octave/3.7.7+/ mkoctfile
--link-stand-alone -o embedded embedded.cc
$ LD_LIBRARY_PATH=/opt/octave/current/lib/octave/3.7.7+/ ./embedded
GCD of [10, 15] is 5
Segmentation fault: 11
$ otool -L embedded
embedded:
/opt/octave/3.7/lib/octave/3.7.7+/liboctinterp.1.dylib (compatibility
version 2.0.0, current version 2.1.0)
/opt/octave/3.7/lib/octave/3.7.7+/liboctave.1.dylib (compatibility
version 2.0.0, current version 2.1.0)
/opt/local/lib/libgcc/libstdc++.6.dylib (compatibility version 7.0.0,
current version 7.18.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 169.3.0)
/opt/local/lib/libgcc/libgcc_s.1.dylib (compatibility version 1.0.0,
current version 1.0.0)
$
anything else I should do to make sure?
> It might help if someone could bisect and find out when this problem
> started happening.
I'm currently reinstalling all Octave dependencies to try build the OSX app
bundle
so my computer is gonna be busy for a while, I'll try bisect when its done,
unless
someone else does that first ...
c.