Csound Csound-dev Csound-tekno Search About

[Cs-dev] mavericks seg fault

Date2014-09-08 21:51
FromBen Hackbarth
Subject[Cs-dev] mavericks seg fault
AttachmentsNone  None  
Hi all,

upgraded (begrudgingly) to osx 10.9.4 and am compiling from the latest git without errors.  however csound exits with an immediate seg fault and i’ve noticed that the csound binary isn’t linked to the framework's full path:

$ otool -L /usr/local/bin/csound
/usr/local/bin/csound:
CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

or perhaps something else is amiss?  here is my cmake call:

sudo cmake CMakeLists.txt -DCMAKE_BUILD_TYPE=Release -DUSE_DOUBLE:BOOL=ON -DBUILD_MULTI_CORE:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_JAVA_INTERFACE:BOOL=OFF -DNEW_PARSER_DEBUG:BOOL=ON -DUSE_PORTMIDI:BOOL=OFF -DPORTAUDIO_LIBRARY:FILEPATH=/usr/local/lib/libportaudio.dylib -DPORTAUDIO_HEADER:FILEPATH=/usr/local/include/portaudio.h -DPYTHON_INCLUDE_DIR=/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/ -DPYTHON_LIBRARY:FILEPATH=/System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib -DSWIG_EXECUTABLE:FILEPATH=/usr/local/bin/swig -DSWIG_DIR:PATH=/usr/local/share/swig/3.0.2/ 

thanks for any insight,
– Ben

°º•ø,,¸¸,,ø-•º°`°º•ø,¸ø•°º•¸

Dr. Ben Hackbarth
Lecturer & Head of Composition
School of Music, University of Liverpool
80-82 Bedford Street South, L69 7WW
+44(0)151 794 3099



Date2014-09-08 22:06
FromVictor Lazzarini
SubjectRe: [Cs-dev] mavericks seg fault
That’s OK as far as the linking is concerned. It means you are linking to a framework that can be either
in ~/Library/Frameworks or in /Library/Frameworks (whichever one exists, the first one is looked for first). 
It is possible that your OPCODE6DIR64 is pointing to the wrong opcodedir and the crash is the result of that.

If you build with make && sudo make install, then your OPCODE6DIR64 should be ~/Library/Frameworks/CsoundLib64.framework/versions/6.0/Resources/Opcodes64
(and that is the default if the environment variable is not set).

========================
Dr Victor Lazzarini
Dean of Arts, Philosophy and Celtic Studies,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 








On 8 Sep 2014, at 21:51, Ben Hackbarth  wrote:

> Hi all,
> 
> upgraded (begrudgingly) to osx 10.9.4 and am compiling from the latest git without errors.  however csound exits with an immediate seg fault and i’ve noticed that the csound binary isn’t linked to the framework's full path:
> 
> $ otool -L /usr/local/bin/csound
> /usr/local/bin/csound:
> 	CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0)
> 	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
> 
> or perhaps something else is amiss?  here is my cmake call:
> 
> sudo cmake CMakeLists.txt -DCMAKE_BUILD_TYPE=Release -DUSE_DOUBLE:BOOL=ON -DBUILD_MULTI_CORE:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_JAVA_INTERFACE:BOOL=OFF -DNEW_PARSER_DEBUG:BOOL=ON -DUSE_PORTMIDI:BOOL=OFF -DPORTAUDIO_LIBRARY:FILEPATH=/usr/local/lib/libportaudio.dylib -DPORTAUDIO_HEADER:FILEPATH=/usr/local/include/portaudio.h -DPYTHON_INCLUDE_DIR=/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/ -DPYTHON_LIBRARY:FILEPATH=/System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib -DSWIG_EXECUTABLE:FILEPATH=/usr/local/bin/swig -DSWIG_DIR:PATH=/usr/local/share/swig/3.0.2/ 
> 
> thanks for any insight,
> – Ben
> 
> °º•ø,,¸¸,,ø-•º°`°º•ø,¸ø•°º•¸
> 
> Dr. Ben Hackbarth
> Lecturer & Head of Composition
> School of Music, University of Liverpool
> 80-82 Bedford Street South, L69 7WW
> +44(0)151 794 3099
> 
> www.benhackbarth.com
> 
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2014-09-08 22:21
FromSteven Yi
SubjectRe: [Cs-dev] mavericks seg fault
Also, if you're using the develop branch, be sure to wipe out any old
csound opcode libraries as they will be binary incompatible with the
develop branch.  Easiest thing would be to rm -r
~/Library/Frameworks/CsoundLib64.framework (or move out it out of the
way).

On Mon, Sep 8, 2014 at 10:06 PM, Victor Lazzarini
 wrote:
> That’s OK as far as the linking is concerned. It means you are linking to a framework that can be either
> in ~/Library/Frameworks or in /Library/Frameworks (whichever one exists, the first one is looked for first).
> It is possible that your OPCODE6DIR64 is pointing to the wrong opcodedir and the crash is the result of that.
>
> If you build with make && sudo make install, then your OPCODE6DIR64 should be ~/Library/Frameworks/CsoundLib64.framework/versions/6.0/Resources/Opcodes64
> (and that is the default if the environment variable is not set).
>
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Philosophy and Celtic Studies,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>
>
>
>
>
>
>
> On 8 Sep 2014, at 21:51, Ben Hackbarth  wrote:
>
>> Hi all,
>>
>> upgraded (begrudgingly) to osx 10.9.4 and am compiling from the latest git without errors.  however csound exits with an immediate seg fault and i’ve noticed that the csound binary isn’t linked to the framework's full path:
>>
>> $ otool -L /usr/local/bin/csound
>> /usr/local/bin/csound:
>>       CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0)
>>       /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
>>
>> or perhaps something else is amiss?  here is my cmake call:
>>
>> sudo cmake CMakeLists.txt -DCMAKE_BUILD_TYPE=Release -DUSE_DOUBLE:BOOL=ON -DBUILD_MULTI_CORE:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_JAVA_INTERFACE:BOOL=OFF -DNEW_PARSER_DEBUG:BOOL=ON -DUSE_PORTMIDI:BOOL=OFF -DPORTAUDIO_LIBRARY:FILEPATH=/usr/local/lib/libportaudio.dylib -DPORTAUDIO_HEADER:FILEPATH=/usr/local/include/portaudio.h -DPYTHON_INCLUDE_DIR=/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/ -DPYTHON_LIBRARY:FILEPATH=/System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib -DSWIG_EXECUTABLE:FILEPATH=/usr/local/bin/swig -DSWIG_DIR:PATH=/usr/local/share/swig/3.0.2/
>>
>> thanks for any insight,
>> – Ben
>>
>> °º•ø,,¸¸,,ø-•º°`°º•ø,¸ø•°º•¸
>>
>> Dr. Ben Hackbarth
>> Lecturer & Head of Composition
>> School of Music, University of Liverpool
>> 80-82 Bedford Street South, L69 7WW
>> +44(0)151 794 3099
>>
>> www.benhackbarth.com
>>
>> ------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce
>> Perforce version control. Predictably reliable.
>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listi

Date2014-09-08 22:26
FromBen Hackbarth
SubjectRe: [Cs-dev] mavericks seg fault
AttachmentsNone  None  
That was it, thanks to you both!
 – ben

On 8 Sep 2014, at 22:21, Steven Yi <stevenyi@gmail.com> wrote:

Also, if you're using the develop branch, be sure to wipe out any old
csound opcode libraries as they will be binary incompatible with the
develop branch.  Easiest thing would be to rm -r
~/Library/Frameworks/CsoundLib64.framework (or move out it out of the
way).

On Mon, Sep 8, 2014 at 10:06 PM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
That’s OK as far as the linking is concerned. It means you are linking to a framework that can be either
in ~/Library/Frameworks or in /Library/Frameworks (whichever one exists, the first one is looked for first).
It is possible that your OPCODE6DIR64 is pointing to the wrong opcodedir and the crash is the result of that.

If you build with make && sudo make install, then your OPCODE6DIR64 should be ~/Library/Frameworks/CsoundLib64.framework/versions/6.0/Resources/Opcodes64
(and that is the default if the environment variable is not set).

========================
Dr Victor Lazzarini
Dean of Arts, Philosophy and Celtic Studies,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952








On 8 Sep 2014, at 21:51, Ben Hackbarth <hackbarth@gmail.com> wrote:

Hi all,

upgraded (begrudgingly) to osx 10.9.4 and am compiling from the latest git without errors.  however csound exits with an immediate seg fault and i’ve noticed that the csound binary isn’t linked to the framework's full path:

$ otool -L /usr/local/bin/csound
/usr/local/bin/csound:
     CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0)
     /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

or perhaps something else is amiss?  here is my cmake call:

sudo cmake CMakeLists.txt -DCMAKE_BUILD_TYPE=Release -DUSE_DOUBLE:BOOL=ON -DBUILD_MULTI_CORE:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_JAVA_INTERFACE:BOOL=OFF -DNEW_PARSER_DEBUG:BOOL=ON -DUSE_PORTMIDI:BOOL=OFF -DPORTAUDIO_LIBRARY:FILEPATH=/usr/local/lib/libportaudio.dylib -DPORTAUDIO_HEADER:FILEPATH=/usr/local/include/portaudio.h -DPYTHON_INCLUDE_DIR=/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/ -DPYTHON_LIBRARY:FILEPATH=/System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib -DSWIG_EXECUTABLE:FILEPATH=/usr/local/bin/swig -DSWIG_DIR:PATH=/usr/local/share/swig/3.0.2/

thanks for any insight,
– Ben

°º•ø,,¸¸,,ø-•º°`°º•ø,¸ø•°º•¸

Dr. Ben Hackbarth
Lecturer & Head of Composition
School of Music, University of Liverpool
80-82 Bedford Street South, L69 7WW
+44(0)151 794 3099

www.benhackbarth.com

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel