Hi,

I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:

:: Csound tidy up: Segmentation fault
:: end of score.		   overall amps:      0.0
:: 	   overall samples out of range:        0
:: 0 errors in performance
:: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s

It seemed to mean that I didn’t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
csound5.18.031-OSX10.7-universal.dmg

I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
csound6.00.0-OSX10.6-x86_64.dmg
csound6.00.0-OSX10.8-x86_64.dmg
csound6.00.1-OSX10.8-x86_64.dmg
csound6.01.0u1-OSX10.8-x86_64.dmg
Csound6.02.0-OSX10.9-x86_64.dmg
csound6.03.2-OSX10.9-universal.dmg

The only version I still get to work is:
csound5.18.031-OSX10.7-universal.dmg
Even though my system is now upgraded.

Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.

Best
Ruben Gjertsen

Could you post the CSD that causes the segfault?

========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 3 Jul 2014, at 17:06, Ruben Sverre Gjertsen  wrote:

> Hi,
> 
> I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:
> 
> :: Csound tidy up: Segmentation fault
> :: end of score.		   overall amps:      0.0
> :: 	   overall samples out of range:        0
> :: 0 errors in performance
> :: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s
> 
> It seemed to mean that I didn’t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
> csound5.18.031-OSX10.7-universal.dmg
> 
> I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
> csound6.00.0-OSX10.6-x86_64.dmg
> csound6.00.0-OSX10.8-x86_64.dmg
> csound6.00.1-OSX10.8-x86_64.dmg
> csound6.01.0u1-OSX10.8-x86_64.dmg
> Csound6.02.0-OSX10.9-x86_64.dmg
> csound6.03.2-OSX10.9-universal.dmg
> 
> The only version I still get to work is:
> csound5.18.031-OSX10.7-universal.dmg
> Even though my system is now upgraded.
> 
> Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.
> 
> Best
> Ruben Gjertsen
> 
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 

Yes, I have a standard setup which I use, there is a Csound Workspace for download here:
http://www.bek.no/~ruben/Research/Downloads/software.html

The folder 0RubenCsound must be placed on root level (./ does not solve relative paths in all cases), and runs with a command like:
csound /0RubenCsound/zAnimalGlassDemoScore1.csd -A -3

These files have the same issue, I have to stick with version 5.18 for them to work.

Ruben


3. juli 2014 kl. 18:12 skrev Victor Lazzarini :

> Could you post the CSD that causes the segfault?
> 
> ========================
> Dr Victor Lazzarini
> Senior Lecturer
> NUI Maynooth, Ireland
> victor dot lazzarini at nuim dot ie
> 
> 
> 
> 
> On 3 Jul 2014, at 17:06, Ruben Sverre Gjertsen  wrote:
> 
>> Hi,
>> 
>> I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:
>> 
>> :: Csound tidy up: Segmentation fault
>> :: end of score.		   overall amps:      0.0
>> :: 	   overall samples out of range:        0
>> :: 0 errors in performance
>> :: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s
>> 
>> It seemed to mean that I didn’t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
>> csound5.18.031-OSX10.7-universal.dmg
>> 
>> I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
>> csound6.00.0-OSX10.6-x86_64.dmg
>> csound6.00.0-OSX10.8-x86_64.dmg
>> csound6.00.1-OSX10.8-x86_64.dmg
>> csound6.01.0u1-OSX10.8-x86_64.dmg
>> Csound6.02.0-OSX10.9-x86_64.dmg
>> csound6.03.2-OSX10.9-universal.dmg
>> 
>> The only version I still get to work is:
>> csound5.18.031-OSX10.7-universal.dmg
>> Even though my system is now upgraded.
>> 
>> Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.
>> 
>> Best
>> Ruben Gjertsen
>> 
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
>> 
>> 
> 
> 
> 
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 

There is a problem with macros. If the code runs on 5.18 and is not running >= 6.00, then it’s a bug
with the macro system. 

It might be hard to track down. I got this backtrace

(lldb) bt
* thread #1: tid = 0x6b563, 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x68)
  * frame #0: 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18
    frame #1: 0x00007fff9ad8ac06 libsystem_c.dylib`fread + 31
    frame #2: 0x000000010018ba8c CsoundLib64`yy_get_next_buffer(yyscanner=0x000000010104c080) + 652 at csound_prelex.c:2308
    frame #3: 0x0000000100184a6c CsoundLib64`csound_prelex(csound=0x0000000100801200, yyscanner=) + 1228 at csound_prelex.c:2149
    frame #4: 0x000000010019a26b CsoundLib64`csoundParseOrc(csound=0x0000000100801200, str=) + 507 at new_orc_parser.c:177
    frame #5: 0x000000010019966c CsoundLib64`csoundCompileOrc(csound=0x0000000100801200, str=) + 12 at csound_orc_compile.c:1684
    frame #6: 0x0000000100104ee4 CsoundLib64`csoundCompileArgs(csound=0x0000000100801200, argc=, argv=) + 1124 at main.c:234
    frame #7: 0x0000000100105829 CsoundLib64`csoundCompile(csound=0x0000000100801200, argc=, argv=) + 9 at main.c:487
    frame #8: 0x0000000100001cf2 csound`main(argc=2, argv=0x00007fff5fbff9f8) + 450 at csound_main.c:133
    frame #9: 0x0000000100001b24 csound`start + 52

which indicates it is crashing in the lexer. 

The macro that is creating he crash is

# define CreateEqualsFFTsettings4method(A) #
ifftsize1=(imethod==$A&&ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
ifftsize2=(imethod==$A&&ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
iolaps1=(imethod==$A&&iolaps1>iolaps2?iolaps2:iolaps1) 
iolaps2=(imethod==$A&&iolaps2>iolaps1?iolaps1:iolaps2) 
;print ifftsize1,iolaps1, imethod
;print ifftsize2,iolaps2, imethod
#

when called as

$CreateEqualsFFTsettings4method(17)

I can’t see anything obvious. Would it be a memory thing I wonder.

========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 3 Jul 2014, at 17:56, jpff@cs.bath.ac.uk wrote:

> Running with -v can also be useful in finding/pinpointing errors.
> 
> Not sure which csd file you are using though
> ==John
> 
> Quoting Ruben Sverre Gjertsen :
> 
>> Yes, I have a standard setup which I use, there is a Csound Workspace for download here:
>> http://www.bek.no/~ruben/Research/Downloads/software.html
>> 
>> The folder 0RubenCsound must be placed on root level (./ does not solve relative paths in all cases), and runs with a command like:
>> csound /0RubenCsound/zAnimalGlassDemoScore1.csd -A -3
>> 
>> These files have the same issue, I have to stick with version 5.18 for them to work.
>> 
>> Ruben
>> 
>> 
>> 3. juli 2014 kl. 18:12 skrev Victor Lazzarini :
>> 
>>> Could you post the CSD that causes the segfault?
>>> 
>>> ========================
>>> Dr Victor Lazzarini
>>> Senior Lecturer
>>> NUI Maynooth, Ireland
>>> victor dot lazzarini at nuim dot ie
>>> 
>>> 
>>> 
>>> 
>>> On 3 Jul 2014, at 17:06, Ruben Sverre Gjertsen  wrote:
>>> 
>>>> Hi,
>>>> 
>>>> I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:
>>>> 
>>>> :: Csound tidy up: Segmentation fault
>>>> :: end of score.		   overall amps:      0.0
>>>> :: 	   overall samples out of range:        0
>>>> :: 0 errors in performance
>>>> :: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s
>>>> 
>>>> It seemed to mean that I didn?t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
>>>> csound5.18.031-OSX10.7-universal.dmg
>>>> 
>>>> I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
>>>> csound6.00.0-OSX10.6-x86_64.dmg
>>>> csound6.00.0-OSX10.8-x86_64.dmg
>>>> csound6.00.1-OSX10.8-x86_64.dmg
>>>> csound6.01.0u1-OSX10.8-x86_64.dmg
>>>> Csound6.02.0-OSX10.9-x86_64.dmg
>>>> csound6.03.2-OSX10.9-universal.dmg
>>>> 
>>>> The only version I still get to work is:
>>>> csound5.18.031-OSX10.7-universal.dmg
>>>> Even though my system is now upgraded.
>>>> 
>>>> Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.
>>>> 
>>>> Best
>>>> Ruben Gjertsen
>>>> 
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 
> 
> 
> Send bugs reports to
>       https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 

I figured it out. If the last line of your macro is a comment, then you need to give it another blank
line before closing it.

# define CreateEqualsFFTsettings4method(A) #
ifftsize1=(imethod== $A && ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
ifftsize2=(imethod== $A && ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
iolaps1=(imethod== $A && iolaps1>iolaps2?iolaps2:iolaps1) 
iolaps2=(imethod== $A && iolaps2>iolaps1?iolaps1:iolaps2) 
;print ifftsize1,iolaps1, imethod
;print ifftsize2,iolaps2, imethod
#

will crash, whereas

# define CreateEqualsFFTsettings4method(A) #
ifftsize1=(imethod== $A && ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
ifftsize2=(imethod== $A && ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
iolaps1=(imethod== $A && iolaps1>iolaps2?iolaps2:iolaps1) 
iolaps2=(imethod== $A && iolaps2>iolaps1?iolaps1:iolaps2) 
;print ifftsize1,iolaps1, imethod
;print ifftsize2,iolaps2, imethod

#

will not. 

I had noticed this before with something reported by Oeyvind; not sure what the story is in
terms of this being a bug or not.

I’ve fixed your macros (see attached). Let me know if it works for you now.

========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 3 Jul 2014, at 18:24, Victor Lazzarini  wrote:

> There is a problem with macros. If the code runs on 5.18 and is not running >= 6.00, then it’s a bug
> with the macro system. 
> 
> It might be hard to track down. I got this backtrace
> 
> (lldb) bt
> * thread #1: tid = 0x6b563, 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x68)
>  * frame #0: 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18
>    frame #1: 0x00007fff9ad8ac06 libsystem_c.dylib`fread + 31
>    frame #2: 0x000000010018ba8c CsoundLib64`yy_get_next_buffer(yyscanner=0x000000010104c080) + 652 at csound_prelex.c:2308
>    frame #3: 0x0000000100184a6c CsoundLib64`csound_prelex(csound=0x0000000100801200, yyscanner=) + 1228 at csound_prelex.c:2149
>    frame #4: 0x000000010019a26b CsoundLib64`csoundParseOrc(csound=0x0000000100801200, str=) + 507 at new_orc_parser.c:177
>    frame #5: 0x000000010019966c CsoundLib64`csoundCompileOrc(csound=0x0000000100801200, str=) + 12 at csound_orc_compile.c:1684
>    frame #6: 0x0000000100104ee4 CsoundLib64`csoundCompileArgs(csound=0x0000000100801200, argc=, argv=) + 1124 at main.c:234
>    frame #7: 0x0000000100105829 CsoundLib64`csoundCompile(csound=0x0000000100801200, argc=, argv=) + 9 at main.c:487
>    frame #8: 0x0000000100001cf2 csound`main(argc=2, argv=0x00007fff5fbff9f8) + 450 at csound_main.c:133
>    frame #9: 0x0000000100001b24 csound`start + 52
> 
> which indicates it is crashing in the lexer. 
> 
> The macro that is creating he crash is
> 
> # define CreateEqualsFFTsettings4method(A) #
> ifftsize1=(imethod==$A&&ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
> ifftsize2=(imethod==$A&&ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
> iolaps1=(imethod==$A&&iolaps1>iolaps2?iolaps2:iolaps1) 
> iolaps2=(imethod==$A&&iolaps2>iolaps1?iolaps1:iolaps2) 
> ;print ifftsize1,iolaps1, imethod
> ;print ifftsize2,iolaps2, imethod
> #
> 
> when called as
> 
> $CreateEqualsFFTsettings4method(17)
> 
> I can’t see anything obvious. Would it be a memory thing I wonder.
> 
> ========================
> Dr Victor Lazzarini
> Senior Lecturer
> NUI Maynooth, Ireland
> victor dot lazzarini at nuim dot ie
> 
> 
> 
> 
> On 3 Jul 2014, at 17:56, jpff@cs.bath.ac.uk wrote:
> 
>> Running with -v can also be useful in finding/pinpointing errors.
>> 
>> Not sure which csd file you are using though
>> ==John
>> 
>> Quoting Ruben Sverre Gjertsen :
>> 
>>> Yes, I have a standard setup which I use, there is a Csound Workspace for download here:
>>> http://www.bek.no/~ruben/Research/Downloads/software.html
>>> 
>>> The folder 0RubenCsound must be placed on root level (./ does not solve relative paths in all cases), and runs with a command like:
>>> csound /0RubenCsound/zAnimalGlassDemoScore1.csd -A -3
>>> 
>>> These files have the same issue, I have to stick with version 5.18 for them to work.
>>> 
>>> Ruben
>>> 
>>> 
>>> 3. juli 2014 kl. 18:12 skrev Victor Lazzarini :
>>> 
>>>> Could you post the CSD that causes the segfault?
>>>> 
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Senior Lecturer
>>>> NUI Maynooth, Ireland
>>>> victor dot lazzarini at nuim dot ie
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 3 Jul 2014, at 17:06, Ruben Sverre Gjertsen  wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:
>>>>> 
>>>>> :: Csound tidy up: Segmentation fault
>>>>> :: end of score.		   overall amps:      0.0
>>>>> :: 	   overall samples out of range:        0
>>>>> :: 0 errors in performance
>>>>> :: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s
>>>>> 
>>>>> It seemed to mean that I didn?t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
>>>>> csound5.18.031-OSX10.7-universal.dmg
>>>>> 
>>>>> I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
>>>>> csound6.00.0-OSX10.6-x86_64.dmg
>>>>> csound6.00.0-OSX10.8-x86_64.dmg
>>>>> csound6.00.1-OSX10.8-x86_64.dmg
>>>>> csound6.01.0u1-OSX10.8-x86_64.dmg
>>>>> Csound6.02.0-OSX10.9-x86_64.dmg
>>>>> csound6.03.2-OSX10.9-universal.dmg
>>>>> 
>>>>> The only version I still get to work is:
>>>>> csound5.18.031-OSX10.7-universal.dmg
>>>>> Even though my system is now upgraded.
>>>>> 
>>>>> Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.
>>>>> 
>>>>> Best
>>>>> Ruben Gjertsen
>>>>> 
>>>>> Send bugs reports to
>>>>>     https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
>> 
>> 
>> 
>> 
>> Send bugs reports to
>>      https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
>> 
>> 
> 
> 
> 
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 

Thank you! Now it works for me too.
Ruben


Den 3. juli 2014 kl. 19.57 skrev Victor Lazzarini:

> I figured it out. If the last line of your macro is a comment, then you need to give it another blank
> line before closing it.
> 
> # define CreateEqualsFFTsettings4method(A) #
> ifftsize1=(imethod== $A && ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
> ifftsize2=(imethod== $A && ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
> iolaps1=(imethod== $A && iolaps1>iolaps2?iolaps2:iolaps1) 
> iolaps2=(imethod== $A && iolaps2>iolaps1?iolaps1:iolaps2) 
> ;print ifftsize1,iolaps1, imethod
> ;print ifftsize2,iolaps2, imethod
> #
> 
> will crash, whereas
> 
> # define CreateEqualsFFTsettings4method(A) #
> ifftsize1=(imethod== $A && ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
> ifftsize2=(imethod== $A && ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
> iolaps1=(imethod== $A && iolaps1>iolaps2?iolaps2:iolaps1) 
> iolaps2=(imethod== $A && iolaps2>iolaps1?iolaps1:iolaps2) 
> ;print ifftsize1,iolaps1, imethod
> ;print ifftsize2,iolaps2, imethod
> 
> #
> 
> will not. 
> 
> I had noticed this before with something reported by Oeyvind; not sure what the story is in
> terms of this being a bug or not.
> 
> I’ve fixed your macros (see attached). Let me know if it works for you now.
> 
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 
> <0RubenCsoundMacros2012.h>
> ========================
> Dr Victor Lazzarini
> Senior Lecturer
> NUI Maynooth, Ireland
> victor dot lazzarini at nuim dot ie
> 
> 
> 
> 
> On 3 Jul 2014, at 18:24, Victor Lazzarini  wrote:
> 
>> There is a problem with macros. If the code runs on 5.18 and is not running >= 6.00, then it’s a bug
>> with the macro system. 
>> 
>> It might be hard to track down. I got this backtrace
>> 
>> (lldb) bt
>> * thread #1: tid = 0x6b563, 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x68)
>> * frame #0: 0x00007fff9ad88eca libsystem_c.dylib`flockfile + 18
>>   frame #1: 0x00007fff9ad8ac06 libsystem_c.dylib`fread + 31
>>   frame #2: 0x000000010018ba8c CsoundLib64`yy_get_next_buffer(yyscanner=0x000000010104c080) + 652 at csound_prelex.c:2308
>>   frame #3: 0x0000000100184a6c CsoundLib64`csound_prelex(csound=0x0000000100801200, yyscanner=) + 1228 at csound_prelex.c:2149
>>   frame #4: 0x000000010019a26b CsoundLib64`csoundParseOrc(csound=0x0000000100801200, str=) + 507 at new_orc_parser.c:177
>>   frame #5: 0x000000010019966c CsoundLib64`csoundCompileOrc(csound=0x0000000100801200, str=) + 12 at csound_orc_compile.c:1684
>>   frame #6: 0x0000000100104ee4 CsoundLib64`csoundCompileArgs(csound=0x0000000100801200, argc=, argv=) + 1124 at main.c:234
>>   frame #7: 0x0000000100105829 CsoundLib64`csoundCompile(csound=0x0000000100801200, argc=, argv=) + 9 at main.c:487
>>   frame #8: 0x0000000100001cf2 csound`main(argc=2, argv=0x00007fff5fbff9f8) + 450 at csound_main.c:133
>>   frame #9: 0x0000000100001b24 csound`start + 52
>> 
>> which indicates it is crashing in the lexer. 
>> 
>> The macro that is creating he crash is
>> 
>> # define CreateEqualsFFTsettings4method(A) #
>> ifftsize1=(imethod==$A&&ifftsize1>ifftsize2?ifftsize2:ifftsize1) 
>> ifftsize2=(imethod==$A&&ifftsize2>ifftsize1?ifftsize1:ifftsize2) 
>> iolaps1=(imethod==$A&&iolaps1>iolaps2?iolaps2:iolaps1) 
>> iolaps2=(imethod==$A&&iolaps2>iolaps1?iolaps1:iolaps2) 
>> ;print ifftsize1,iolaps1, imethod
>> ;print ifftsize2,iolaps2, imethod
>> #
>> 
>> when called as
>> 
>> $CreateEqualsFFTsettings4method(17)
>> 
>> I can’t see anything obvious. Would it be a memory thing I wonder.
>> 
>> ========================
>> Dr Victor Lazzarini
>> Senior Lecturer
>> NUI Maynooth, Ireland
>> victor dot lazzarini at nuim dot ie
>> 
>> 
>> 
>> 
>> On 3 Jul 2014, at 17:56, jpff@cs.bath.ac.uk wrote:
>> 
>>> Running with -v can also be useful in finding/pinpointing errors.
>>> 
>>> Not sure which csd file you are using though
>>> ==John
>>> 
>>> Quoting Ruben Sverre Gjertsen :
>>> 
>>>> Yes, I have a standard setup which I use, there is a Csound Workspace for download here:
>>>> http://www.bek.no/~ruben/Research/Downloads/software.html
>>>> 
>>>> The folder 0RubenCsound must be placed on root level (./ does not solve relative paths in all cases), and runs with a command like:
>>>> csound /0RubenCsound/zAnimalGlassDemoScore1.csd -A -3
>>>> 
>>>> These files have the same issue, I have to stick with version 5.18 for them to work.
>>>> 
>>>> Ruben
>>>> 
>>>> 
>>>> 3. juli 2014 kl. 18:12 skrev Victor Lazzarini :
>>>> 
>>>>> Could you post the CSD that causes the segfault?
>>>>> 
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Senior Lecturer
>>>>> NUI Maynooth, Ireland
>>>>> victor dot lazzarini at nuim dot ie
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 3 Jul 2014, at 17:06, Ruben Sverre Gjertsen  wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> I have been looking for working Csound versions on Osx 10.6.8 for a while. Many versions give the error «segmentation fault» and Csound skips the score:
>>>>>> 
>>>>>> :: Csound tidy up: Segmentation fault
>>>>>> :: end of score.		   overall amps:      0.0
>>>>>> :: 	   overall samples out of range:        0
>>>>>> :: 0 errors in performance
>>>>>> :: Elapsed time at end of performance: real: 0.478s, CPU: 0.025s
>>>>>> 
>>>>>> It seemed to mean that I didn?t choose the right build (OSX10.6 or OSX10.7). This is still the most recent version I got to run my scores:
>>>>>> csound5.18.031-OSX10.7-universal.dmg
>>>>>> 
>>>>>> I thought upgrading to Maverick could help using newer version, but all of the following versions gave the same «segmentation fault» on Osx 10.9.4:
>>>>>> csound6.00.0-OSX10.6-x86_64.dmg
>>>>>> csound6.00.0-OSX10.8-x86_64.dmg
>>>>>> csound6.00.1-OSX10.8-x86_64.dmg
>>>>>> csound6.01.0u1-OSX10.8-x86_64.dmg
>>>>>> Csound6.02.0-OSX10.9-x86_64.dmg
>>>>>> csound6.03.2-OSX10.9-universal.dmg
>>>>>> 
>>>>>> The only version I still get to work is:
>>>>>> csound5.18.031-OSX10.7-universal.dmg
>>>>>> Even though my system is now upgraded.
>>>>>> 
>>>>>> Do you have some hints about what kind of systems Csound 6 can run on? It would be nice to be able to follow new upgrades.
>>>>>> 
>>>>>> Best
>>>>>> Ruben Gjertsen
>>>>>> 
>>>>>> Send bugs reports to
>>>>>>    https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Send bugs reports to
>>>>>     https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Send bugs reports to
>>>     https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
>> 
>> 
>