Csound Csound-dev Csound-tekno Search About

[Csnd] Git master master segfaults on toot01

Date2011-12-17 00:17
FromJeremy Henty
Subject[Csnd] Git master master segfaults on toot01
AttachmentsNone  None  toot01.orc  toot01.sco  csound_test_log__bad.txt  csound_test_log__bad_parent.txt  

Date2011-12-17 00:42
FromSteven Yi
SubjectRe: [Csnd] Git master master segfaults on toot01
Hi Jeremy,

It looks like you have a lot of opcode libs in your OPCODEDIR or OPCODEDIR64 that are old.  Could you try clearing everything out and using only the new stuff that was built?  A lot of opcodes were merged into libcsound from being individual opcode libraries and I think there are conflicts if you don't clean out the old ones.  If anything, we should make sure that is done first to help diagnose.

Thanks!
steven

On Sat, Dec 17, 2011 at 12:17 AM, Jeremy Henty <onepoint@starurchin.org> wrote:

Git  bisect identifies  the bad  commit as  "766f2a7 more  tidying and
include  directory in  score".   Unfortunately that's  something of  a
portmanteau  commit so  I  don't know  where  to look  next.  I  would
appreciate any guidance.

Orchestra, score and test output files attached.

Regards,

Jeremy Henty

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



Date2011-12-17 10:18
Fromjpff@cs.bath.ac.uk
SubjectRe: [Csnd] Git master master segfaults on toot01
The answer is in the messages!  The change between API 2.5 and 2.6 reflect
that most opcodes are now in the bases.  You need to run clean.sh abd then
scons

==John ff

>
> Git  bisect identifies  the bad  commit as  "766f2a7 more  tidying and
> include  directory in  score".   Unfortunately that's  something of  a
> portmanteau  commit so  I  don't know  where  to look  next.  I  would
> appreciate any guidance.
>
> Orchestra, score and test output files attached.
>
> Regards,
>
> Jeremy Henty
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2011-12-17 11:59
FromJeremy Henty
SubjectRe: [Csnd] Git master master segfaults on toot01
AttachmentsNone  None  toot01.orc  toot01.sco  csound_test_log__bad_parent.txt  csound_test_log__bad.txt  

Date2011-12-17 12:02
FromJeremy Henty
SubjectRe: [Csnd] Git master master segfaults on toot01
AttachmentsNone  

Date2011-12-17 12:28
Fromjpff@cs.bath.ac.uk
SubjectRe: [Csnd] Git master master segfaults on toot01
initial testys suggest that thi sis an orc/sco issue.  I get no0 problem
with toot1.csd.  More soon

>
> jpff@cs.bath.ac.uk wrote:
>
>> The answer is in the messages!  The change between API 2.5 and 2.6
>> reflect
>> that most opcodes are now in the bases.  You need to run clean.sh abd
>> then
>> scons
>
> Thanks!   However  that only  removes  the  opcode  warnings, not  the
> problem.  "766f2a7 more tidying  and include directory in score" still
> segfaults and its parent does not.  Updated logs attached.
>
> Regards,
>
> Jeremy Henty
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2011-12-17 13:05
Fromjpff@cs.bath.ac.uk
SubjectRe: [Csnd] Git master master segfaults on toot01
> initial testys suggest that thi sis an orc/sco issue.  I get no0 problem
> with toot1.csd.  More soon
>

Looks like double closing of the orc and sco files.  Will take a little
while to fix.  And as I said only refers to orc/sco pairs

==John ff



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2011-12-17 13:14
Fromjpff@cs.bath.ac.uk
SubjectRe: [Csnd] Git master master segfaults on toot01
Believed fixed and in git






Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2011-12-17 14:45
FromJeremy Henty
SubjectRe: [Csnd] Git master master segfaults on toot01
AttachmentsNone