Greetings,

While working with the latest Cabbage I discovered that the latest 
Csound git pull produced a binary that makes the Cabbage synths 
unusable. I've reported the issue to Rory, but the problem is apparently 
with Csound, not Cabbage.

I have Csound 6.04 running on two machines. The build on the laptop is 
dated Dec 8 2014, the build on the desktop is from a fresh git pull 
yesterday morning (March 10 2015). Synths built with Cabbage run fine on 
the laptop but segfault on the desktop box.

I ran Cabbage and Csound through gdb for a backtrace. Here's something 
from the latest report after attempting to run the choir.csd synth:

allocate label __synthetic_300
...
allocate label __synthetic_319

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
Missing separate debuginfos...

(gdb) thread apply all bt

Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
#0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
#1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
#2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
#3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
#4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
#5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
#6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
#7  0x000000000040177f in main ()
(gdb)

All segfaulting synths create the same error. m_chinsno is from the 
midiops header, which hasn't been changed for a while, so I'm at a loss 
from this point. Can anyone suggest what changed in Csound to create 
this incompatibility ?

Btw, I copied the Csound source from my laptop to the desktop box, 
recompiled and reinstalled, and all the Cabbage synths work again. That 
test seems to point to Csound as the problem. Please advise if more 
information is needed, I'll be happy to work on this issue.

Systems are identical on the machines. Fedora 19, x86_64, with Planet 
CCRMA extensions.

Best,

dp


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

If you build from the develop branch, you will get this from time to time, as we are developing things that
might not be ready to go. To avoid it, you will need to use the master branch.

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

> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
> 
> Greetings,
> 
> While working with the latest Cabbage I discovered that the latest 
> Csound git pull produced a binary that makes the Cabbage synths 
> unusable. I've reported the issue to Rory, but the problem is apparently 
> with Csound, not Cabbage.
> 
> I have Csound 6.04 running on two machines. The build on the laptop is 
> dated Dec 8 2014, the build on the desktop is from a fresh git pull 
> yesterday morning (March 10 2015). Synths built with Cabbage run fine on 
> the laptop but segfault on the desktop box.
> 
> I ran Cabbage and Csound through gdb for a backtrace. Here's something 
> from the latest report after attempting to run the choir.csd synth:
> 
> allocate label __synthetic_300
> ...
> allocate label __synthetic_319
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
> Missing separate debuginfos...
> 
> (gdb) thread apply all bt
> 
> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
> #7  0x000000000040177f in main ()
> (gdb)
> 
> All segfaulting synths create the same error. m_chinsno is from the 
> midiops header, which hasn't been changed for a while, so I'm at a loss 
> from this point. Can anyone suggest what changed in Csound to create 
> this incompatibility ?
> 
> Btw, I copied the Csound source from my laptop to the desktop box, 
> recompiled and reinstalled, and all the Cabbage synths work again. That 
> test seems to point to Csound as the problem. Please advise if more 
> information is needed, I'll be happy to work on this issue.
> 
> Systems are identical on the machines. Fedora 19, x86_64, with Planet 
> CCRMA extensions.
> 
> Best,
> 
> dp
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On 03/11/2015 08:24 AM, Victor Lazzarini wrote:
> If you build from the develop branch, you will get this from time to time, as we are developing things that
> might not be ready to go. To avoid it, you will need to use the master branch.

I know that. I don't care about avoiding the issue, I'd like to resolve 
it. :) I can provide full backtraces if anyone wants to look at them.

Btw, does Csound development currently use anything like Mantis for 
reporting and tracking bugs ?

I have a working codebase on both machines now, but I'll continue to 
monitor and test the development branch. Hopefully the problem will be 
resolved soon.

Best,

dp



> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
>>
>> Greetings,
>>
>> While working with the latest Cabbage I discovered that the latest
>> Csound git pull produced a binary that makes the Cabbage synths
>> unusable. I've reported the issue to Rory, but the problem is apparently
>> with Csound, not Cabbage.
>>
>> I have Csound 6.04 running on two machines. The build on the laptop is
>> dated Dec 8 2014, the build on the desktop is from a fresh git pull
>> yesterday morning (March 10 2015). Synths built with Cabbage run fine on
>> the laptop but segfault on the desktop box.
>>
>> I ran Cabbage and Csound through gdb for a backtrace. Here's something
>> from the latest report after attempting to run the choir.csd synth:
>>
>> allocate label __synthetic_300
>> ...
>> allocate label __synthetic_319
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>> Missing separate debuginfos...
>>
>> (gdb) thread apply all bt
>>
>> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
>> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
>> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
>> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
>> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
>> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
>> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
>> #7  0x000000000040177f in main ()
>> (gdb)
>>
>> All segfaulting synths create the same error. m_chinsno is from the
>> midiops header, which hasn't been changed for a while, so I'm at a loss
>> from this point. Can anyone suggest what changed in Csound to create
>> this incompatibility ?
>>
>> Btw, I copied the Csound source from my laptop to the desktop box,
>> recompiled and reinstalled, and all the Cabbage synths work again. That
>> test seems to point to Csound as the problem. Please advise if more
>> information is needed, I'll be happy to work on this issue.
>>
>> Systems are identical on the machines. Fedora 19, x86_64, with Planet
>> CCRMA extensions.
>>
>> Best,
>>
>> dp
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have fixed this issue already in git, as far as I know.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 11 Mar 2015, at 12:41, Dave Phillips  wrote:
> 
> 
> On 03/11/2015 08:24 AM, Victor Lazzarini wrote:
>> If you build from the develop branch, you will get this from time to time, as we are developing things that
>> might not be ready to go. To avoid it, you will need to use the master branch.
> 
> I know that. I don't care about avoiding the issue, I'd like to resolve 
> it. :) I can provide full backtraces if anyone wants to look at them.
> 
> Btw, does Csound development currently use anything like Mantis for 
> reporting and tracking bugs ?
> 
> I have a working codebase on both machines now, but I'll continue to 
> monitor and test the development branch. Hopefully the problem will be 
> resolved soon.
> 
> Best,
> 
> dp
> 
> 
> 
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
>>> 
>>> Greetings,
>>> 
>>> While working with the latest Cabbage I discovered that the latest
>>> Csound git pull produced a binary that makes the Cabbage synths
>>> unusable. I've reported the issue to Rory, but the problem is apparently
>>> with Csound, not Cabbage.
>>> 
>>> I have Csound 6.04 running on two machines. The build on the laptop is
>>> dated Dec 8 2014, the build on the desktop is from a fresh git pull
>>> yesterday morning (March 10 2015). Synths built with Cabbage run fine on
>>> the laptop but segfault on the desktop box.
>>> 
>>> I ran Cabbage and Csound through gdb for a backtrace. Here's something
>>> from the latest report after attempting to run the choir.csd synth:
>>> 
>>> allocate label __synthetic_300
>>> ...
>>> allocate label __synthetic_319
>>> 
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>> Missing separate debuginfos...
>>> 
>>> (gdb) thread apply all bt
>>> 
>>> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
>>> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
>>> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
>>> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
>>> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
>>> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
>>> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
>>> #7  0x000000000040177f in main ()
>>> (gdb)
>>> 
>>> All segfaulting synths create the same error. m_chinsno is from the
>>> midiops header, which hasn't been changed for a while, so I'm at a loss
>>> from this point. Can anyone suggest what changed in Csound to create
>>> this incompatibility ?
>>> 
>>> Btw, I copied the Csound source from my laptop to the desktop box,
>>> recompiled and reinstalled, and all the Cabbage synths work again. That
>>> test seems to point to Csound as the problem. Please advise if more
>>> information is needed, I'll be happy to work on this issue.
>>> 
>>> Systems are identical on the machines. Fedora 19, x86_64, with Planet
>>> CCRMA extensions.
>>> 
>>> Best,
>>> 
>>> dp
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Or maybe it is something else. I will have a look later.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 11 Mar 2015, at 12:47, Victor Lazzarini  wrote:
> 
> I have fixed this issue already in git, as far as I know.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952 
> 
>> On 11 Mar 2015, at 12:41, Dave Phillips  wrote:
>> 
>> 
>>> On 03/11/2015 08:24 AM, Victor Lazzarini wrote:
>>> If you build from the develop branch, you will get this from time to time, as we are developing things that
>>> might not be ready to go. To avoid it, you will need to use the master branch.
>> 
>> I know that. I don't care about avoiding the issue, I'd like to resolve 
>> it. :) I can provide full backtraces if anyone wants to look at them.
>> 
>> Btw, does Csound development currently use anything like Mantis for 
>> reporting and tracking bugs ?
>> 
>> I have a working codebase on both machines now, but I'll continue to 
>> monitor and test the development branch. Hopefully the problem will be 
>> resolved soon.
>> 
>> Best,
>> 
>> dp
>> 
>> 
>> 
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
>>>> 
>>>> Greetings,
>>>> 
>>>> While working with the latest Cabbage I discovered that the latest
>>>> Csound git pull produced a binary that makes the Cabbage synths
>>>> unusable. I've reported the issue to Rory, but the problem is apparently
>>>> with Csound, not Cabbage.
>>>> 
>>>> I have Csound 6.04 running on two machines. The build on the laptop is
>>>> dated Dec 8 2014, the build on the desktop is from a fresh git pull
>>>> yesterday morning (March 10 2015). Synths built with Cabbage run fine on
>>>> the laptop but segfault on the desktop box.
>>>> 
>>>> I ran Cabbage and Csound through gdb for a backtrace. Here's something
>>>> from the latest report after attempting to run the choir.csd synth:
>>>> 
>>>> allocate label __synthetic_300
>>>> ...
>>>> allocate label __synthetic_319
>>>> 
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>> Missing separate debuginfos...
>>>> 
>>>> (gdb) thread apply all bt
>>>> 
>>>> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
>>>> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
>>>> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
>>>> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
>>>> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
>>>> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
>>>> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
>>>> #7  0x000000000040177f in main ()
>>>> (gdb)
>>>> 
>>>> All segfaulting synths create the same error. m_chinsno is from the
>>>> midiops header, which hasn't been changed for a while, so I'm at a loss
>>>> from this point. Can anyone suggest what changed in Csound to create
>>>> this incompatibility ?
>>>> 
>>>> Btw, I copied the Csound source from my laptop to the desktop box,
>>>> recompiled and reinstalled, and all the Cabbage synths work again. That
>>>> test seems to point to Csound as the problem. Please advise if more
>>>> information is needed, I'll be happy to work on this issue.
>>>> 
>>>> Systems are identical on the machines. Fedora 19, x86_64, with Planet
>>>> CCRMA extensions.
>>>> 
>>>> Best,
>>>> 
>>>> dp
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>> things parallel software development, from weekly thought leadership blogs to
>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>> conversation now. http://goparallel.sourceforge.net/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> 
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> 
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the 
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On 03/11/2015 09:00 AM, Victor Lazzarini wrote:
> Or maybe it is something else. I will have a look later.

You are an ace, Victor, I believe that bug has been shot down. :) Thanks 
a lot, the latest pull compiled and installed cleanly (as usual), and 
the Cabbage synths now work again.

Michael, thanks for the pointer to the github bug list, I'll check it out.

Thanks again, Victor, the fix is greatly appreciated.

Best,

dp



>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 11 Mar 2015, at 12:47, Victor Lazzarini  wrote:
>>
>> I have fixed this issue already in git, as far as I know.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 11 Mar 2015, at 12:41, Dave Phillips  wrote:
>>>
>>>
>>>> On 03/11/2015 08:24 AM, Victor Lazzarini wrote:
>>>> If you build from the develop branch, you will get this from time to time, as we are developing things that
>>>> might not be ready to go. To avoid it, you will need to use the master branch.
>>> I know that. I don't care about avoiding the issue, I'd like to resolve
>>> it. :) I can provide full backtraces if anyone wants to look at them.
>>>
>>> Btw, does Csound development currently use anything like Mantis for
>>> reporting and tracking bugs ?
>>>
>>> I have a working codebase on both machines now, but I'll continue to
>>> monitor and test the development branch. Hopefully the problem will be
>>> resolved soon.
>>>
>>> Best,
>>>
>>> dp
>>>
>>>
>>>
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
>>>>>
>>>>> Greetings,
>>>>>
>>>>> While working with the latest Cabbage I discovered that the latest
>>>>> Csound git pull produced a binary that makes the Cabbage synths
>>>>> unusable. I've reported the issue to Rory, but the problem is apparently
>>>>> with Csound, not Cabbage.
>>>>>
>>>>> I have Csound 6.04 running on two machines. The build on the laptop is
>>>>> dated Dec 8 2014, the build on the desktop is from a fresh git pull
>>>>> yesterday morning (March 10 2015). Synths built with Cabbage run fine on
>>>>> the laptop but segfault on the desktop box.
>>>>>
>>>>> I ran Cabbage and Csound through gdb for a backtrace. Here's something
>>>>> from the latest report after attempting to run the choir.csd synth:
>>>>>
>>>>> allocate label __synthetic_300
>>>>> ...
>>>>> allocate label __synthetic_319
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>>> Missing separate debuginfos...
>>>>>
>>>>> (gdb) thread apply all bt
>>>>>
>>>>> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
>>>>> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>>> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
>>>>> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
>>>>> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
>>>>> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
>>>>> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
>>>>> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
>>>>> #7  0x000000000040177f in main ()
>>>>> (gdb)
>>>>>
>>>>> All segfaulting synths create the same error. m_chinsno is from the
>>>>> midiops header, which hasn't been changed for a while, so I'm at a loss
>>>>> from this point. Can anyone suggest what changed in Csound to create
>>>>> this incompatibility ?
>>>>>
>>>>> Btw, I copied the Csound source from my laptop to the desktop box,
>>>>> recompiled and reinstalled, and all the Cabbage synths work again. That
>>>>> test seems to point to Csound as the problem. Please advise if more
>>>>> information is needed, I'll be happy to work on this issue.
>>>>>
>>>>> Systems are identical on the machines. Fedora 19, x86_64, with Planet
>>>>> CCRMA extensions.
>>>>>
>>>>> Best,
>>>>>
>>>>> dp
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>>> things parallel software development, from weekly thought leadership blogs to
>>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>>> conversation now. http://goparallel.sourceforge.net/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> ------------------------------------------------------------------------------
>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>> things parallel software development, from weekly thought leadership blogs to
>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>> conversation now. http://goparallel.sourceforge.net/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks. Someone had reported a bug last week and I got to it eventually.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 11 Mar 2015, at 13:20, Dave Phillips  wrote:
> 
> 
>> On 03/11/2015 09:00 AM, Victor Lazzarini wrote:
>> Or maybe it is something else. I will have a look later.
> 
> You are an ace, Victor, I believe that bug has been shot down. :) Thanks 
> a lot, the latest pull compiled and installed cleanly (as usual), and 
> the Cabbage synths now work again.
> 
> Michael, thanks for the pointer to the github bug list, I'll check it out.
> 
> Thanks again, Victor, the fix is greatly appreciated.
> 
> Best,
> 
> dp
> 
> 
> 
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 11 Mar 2015, at 12:47, Victor Lazzarini  wrote:
>>> 
>>> I have fixed this issue already in git, as far as I know.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 11 Mar 2015, at 12:41, Dave Phillips  wrote:
>>>> 
>>>> 
>>>>> On 03/11/2015 08:24 AM, Victor Lazzarini wrote:
>>>>> If you build from the develop branch, you will get this from time to time, as we are developing things that
>>>>> might not be ready to go. To avoid it, you will need to use the master branch.
>>>> I know that. I don't care about avoiding the issue, I'd like to resolve
>>>> it. :) I can provide full backtraces if anyone wants to look at them.
>>>> 
>>>> Btw, does Csound development currently use anything like Mantis for
>>>> reporting and tracking bugs ?
>>>> 
>>>> I have a working codebase on both machines now, but I'll continue to
>>>> monitor and test the development branch. Hopefully the problem will be
>>>> resolved soon.
>>>> 
>>>> Best,
>>>> 
>>>> dp
>>>> 
>>>> 
>>>> 
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>> 
>>>>>> On 11 Mar 2015, at 11:53, Dave Phillips  wrote:
>>>>>> 
>>>>>> Greetings,
>>>>>> 
>>>>>> While working with the latest Cabbage I discovered that the latest
>>>>>> Csound git pull produced a binary that makes the Cabbage synths
>>>>>> unusable. I've reported the issue to Rory, but the problem is apparently
>>>>>> with Csound, not Cabbage.
>>>>>> 
>>>>>> I have Csound 6.04 running on two machines. The build on the laptop is
>>>>>> dated Dec 8 2014, the build on the desktop is from a fresh git pull
>>>>>> yesterday morning (March 10 2015). Synths built with Cabbage run fine on
>>>>>> the laptop but segfault on the desktop box.
>>>>>> 
>>>>>> I ran Cabbage and Csound through gdb for a backtrace. Here's something
>>>>>> from the latest report after attempting to run the choir.csd synth:
>>>>>> 
>>>>>> allocate label __synthetic_300
>>>>>> ...
>>>>>> allocate label __synthetic_319
>>>>>> 
>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>> 0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>>>> Missing separate debuginfos...
>>>>>> 
>>>>>> (gdb) thread apply all bt
>>>>>> 
>>>>>> Thread 1 (Thread 0x7ffff763f880 (LWP 4183)):
>>>>>> #0  0x00007ffff7b10bca in m_chinsno () from /lib64/libcsound64.so.6.0
>>>>>> #1  0x00007ffff7b4532d in massign_p () from /lib64/libcsound64.so.6.0
>>>>>> #2  0x00007ffff7ae6259 in init0 () from /lib64/libcsound64.so.6.0
>>>>>> #3  0x00007ffff7d45e8e in csoundCompileTree () from /lib64/libcsound64.so.6.0
>>>>>> #4  0x00007ffff7d45fd2 in csoundCompileOrc () from /lib64/libcsound64.so.6.0
>>>>>> #5  0x00007ffff7c5cf88 in csoundCompileArgs () from /lib64/libcsound64.so.6.0
>>>>>> #6  0x00007ffff7c5de02 in csoundCompile () from /lib64/libcsound64.so.6.0
>>>>>> #7  0x000000000040177f in main ()
>>>>>> (gdb)
>>>>>> 
>>>>>> All segfaulting synths create the same error. m_chinsno is from the
>>>>>> midiops header, which hasn't been changed for a while, so I'm at a loss
>>>>>> from this point. Can anyone suggest what changed in Csound to create
>>>>>> this incompatibility ?
>>>>>> 
>>>>>> Btw, I copied the Csound source from my laptop to the desktop box,
>>>>>> recompiled and reinstalled, and all the Cabbage synths work again. That
>>>>>> test seems to point to Csound as the problem. Please advise if more
>>>>>> information is needed, I'll be happy to work on this issue.
>>>>>> 
>>>>>> Systems are identical on the machines. Fedora 19, x86_64, with Planet
>>>>>> CCRMA extensions.
>>>>>> 
>>>>>> Best,
>>>>>> 
>>>>>> dp
>>>>>> 
>>>>>> 
>>>>>> ------------------------------------------------------------------------------
>>>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>>>> things parallel software development, from weekly thought leadership blogs to
>>>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>>>> conversation now. http://goparallel.sourceforge.net/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>> ------------------------------------------------------------------------------
>>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>>> things parallel software development, from weekly thought leadership blogs to
>>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>>> conversation now. http://goparallel.sourceforge.net/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>>> things parallel software development, from weekly thought leadership blogs to
>>>> news, videos, case studies, tutorials and more. Take a look and join the
>>>> conversation now. http://goparallel.sourceforge.net/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> 
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net