Seg fault - "corrupted double-linked list:"

Seg fault - "corrupted double-linked list:"

Date	2016-05-05 12:12
From	Peter Burgess
Subject	Seg fault - "corrupted double-linked list:"
	Hi Csounders, I'm suddenly getting an error in my app today, and I'm struggling to track it down. It says this: * Error in `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': corrupted double-linked list: 0x0000000003e1cdf0 * Csound tidy up: Aborted It happens on about 70% of runs, and the only things I remember changing before it started was adding some EQ to my master out instrument definition, and changing some "=" to "init"... but I guess I must of done something else too, lol. I've debugged a few times, and it seems to happen in two different places during Csound performance, here are the stack traces from csoundPerform() on: Stack 1: #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) #1 0x7ffff782e8fa kperf_nodebug() (/usr/local/lib/libcsound64.so.6.0:??) #2 0x7ffff783004e csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) #3 0x44f48e Csound::Perform(this=0x6fae90 ) (csound/Csound6.05/include/csound.hpp:273) Stack 2: #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) (../nptl/sysdeps/unix/sysv/linux/raise.c:56) #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") (../sysdeps/posix/libc_fatal.c:175) #3 0x7ffff5f3c0f7 malloc_printerr(action=, str=0x7ffff603bbfc "corrupted double-linked list", ptr=) (malloc.c:4996) #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 , bytes=bytes@entry=80) (malloc.c:3700) #5 0x7ffff5f412cc __libc_calloc(n=, elem_size=) (malloc.c:3219) #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) #7 0x7ffff76b132a csoundAuxAlloc() (/usr/local/lib/libcsound64.so.6.0:??) #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) #10 0x7ffff76d636f process_score_event() (/usr/local/lib/libcsound64.so.6.0:??) #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) #12 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) #13 0x44f48e Csound::Perform(this=0x6fae90 ) (csound/Csound6.05/include/csound.hpp:273) any ideas? Pete

Date	2016-05-05 12:15
From	jpff
Subject	Re: Seg fault - "corrupted double-linked list:"
	Do you hae access to valgrind? That is what I usually use to assist in memory problems -- plus thinking of course. ==John On Thu, 5 May 2016, Peter Burgess wrote: > Hi Csounders, I'm suddenly getting an error in my app today, and I'm > struggling to track it down. It says this: > > * Error in `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': > corrupted double-linked list: 0x0000000003e1cdf0 * > Csound tidy up: Aborted > > It happens on about 70% of runs, and the only things I remember > changing before it started was adding some EQ to my master out > instrument definition, and changing some "=" to "init"... but I guess > I must of done something else too, lol. > > I've debugged a few times, and it seems to happen in two different > places during Csound performance, here are the stack traces from > csoundPerform() on: > > Stack 1: > > #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) > #1 0x7ffff782e8fa kperf_nodebug() (/usr/local/lib/libcsound64.so.6.0:??) > #2 0x7ffff783004e csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) > #3 0x44f48e Csound::Perform(this=0x6fae90 ) > (csound/Csound6.05/include/csound.hpp:273) > > Stack 2: > > #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) > (../nptl/sysdeps/unix/sysv/linux/raise.c:56) > #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) > #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, > fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") > (../sysdeps/posix/libc_fatal.c:175) > #3 0x7ffff5f3c0f7 malloc_printerr(action=, > str=0x7ffff603bbfc "corrupted double-linked list", ptr= out>) (malloc.c:4996) > #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 > , bytes=bytes@entry=80) (malloc.c:3700) > #5 0x7ffff5f412cc __libc_calloc(n=, > elem_size=) (malloc.c:3219) > #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) > #7 0x7ffff76b132a csoundAuxAlloc() (/usr/local/lib/libcsound64.so.6.0:??) > #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) > #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) > #10 0x7ffff76d636f process_score_event() > (/usr/local/lib/libcsound64.so.6.0:??) > #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) > #12 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) > #13 0x44f48e Csound::Perform(this=0x6fae90 ) > (csound/Csound6.05/include/csound.hpp:273) > > any ideas? > > Pete > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 12:17
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	I have got valgrind, but when I last tried to use it, it didn't seem to do anything.... having said that, I might of tried it the time I had an accidental infinate loop in my code somewhere, so it might of just been stuck on an infinite loop.... I'll give it another shot On Thu, May 5, 2016 at 12:15 PM, jpff wrote: > Do you hae access to valgrind? That is what I usually use to assist in > memory problems -- plus thinking of course. > ==John > > > > On Thu, 5 May 2016, Peter Burgess wrote: > >> Hi Csounders, I'm suddenly getting an error in my app today, and I'm >> struggling to track it down. It says this: >> >> * Error in >> `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': >> corrupted double-linked list: 0x0000000003e1cdf0 * >> Csound tidy up: Aborted >> >> It happens on about 70% of runs, and the only things I remember >> changing before it started was adding some EQ to my master out >> instrument definition, and changing some "=" to "init"... but I guess >> I must of done something else too, lol. >> >> I've debugged a few times, and it seems to happen in two different >> places during Csound performance, here are the stack traces from >> csoundPerform() on: >> >> Stack 1: >> >> #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) >> #1 0x7ffff782e8fa kperf_nodebug() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #2 0x7ffff783004e csoundPerform() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #3 0x44f48e Csound::Perform(this=0x6fae90 ) >> (csound/Csound6.05/include/csound.hpp:273) >> >> Stack 2: >> >> #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) >> (../nptl/sysdeps/unix/sysv/linux/raise.c:56) >> #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) >> #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, >> fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") >> (../sysdeps/posix/libc_fatal.c:175) >> #3 0x7ffff5f3c0f7 malloc_printerr(action=, >> str=0x7ffff603bbfc "corrupted double-linked list", ptr=> out>) (malloc.c:4996) >> #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 >> , bytes=bytes@entry=80) (malloc.c:3700) >> #5 0x7ffff5f412cc __libc_calloc(n=, >> elem_size=) (malloc.c:3219) >> #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) >> #7 0x7ffff76b132a csoundAuxAlloc() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) >> #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >> #10 0x7ffff76d636f process_score_event() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >> #12 0x7ffff782ffa8 csoundPerform() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #13 0x44f48e Csound::Perform(this=0x6fae90 ) >> (csound/Csound6.05/include/csound.hpp:273) >> >> any ideas? >> >> Pete >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 12:19
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Ok, it does work.... and it's reporting 2389 errors... eek!!!!! On Thu, May 5, 2016 at 12:17 PM, Peter Burgess wrote: > I have got valgrind, but when I last tried to use it, it didn't seem > to do anything.... having said that, I might of tried it the time I > had an accidental infinate loop in my code somewhere, so it might of > just been stuck on an infinite loop.... I'll give it another shot > > On Thu, May 5, 2016 at 12:15 PM, jpff wrote: >> Do you hae access to valgrind? That is what I usually use to assist in >> memory problems -- plus thinking of course. >> ==John >> >> >> >> On Thu, 5 May 2016, Peter Burgess wrote: >> >>> Hi Csounders, I'm suddenly getting an error in my app today, and I'm >>> struggling to track it down. It says this: >>> >>> * Error in >>> `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': >>> corrupted double-linked list: 0x0000000003e1cdf0 * >>> Csound tidy up: Aborted >>> >>> It happens on about 70% of runs, and the only things I remember >>> changing before it started was adding some EQ to my master out >>> instrument definition, and changing some "=" to "init"... but I guess >>> I must of done something else too, lol. >>> >>> I've debugged a few times, and it seems to happen in two different >>> places during Csound performance, here are the stack traces from >>> csoundPerform() on: >>> >>> Stack 1: >>> >>> #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) >>> #1 0x7ffff782e8fa kperf_nodebug() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #2 0x7ffff783004e csoundPerform() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #3 0x44f48e Csound::Perform(this=0x6fae90 ) >>> (csound/Csound6.05/include/csound.hpp:273) >>> >>> Stack 2: >>> >>> #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) >>> (../nptl/sysdeps/unix/sysv/linux/raise.c:56) >>> #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) >>> #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, >>> fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") >>> (../sysdeps/posix/libc_fatal.c:175) >>> #3 0x7ffff5f3c0f7 malloc_printerr(action=, >>> str=0x7ffff603bbfc "corrupted double-linked list", ptr=>> out>) (malloc.c:4996) >>> #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 >>> , bytes=bytes@entry=80) (malloc.c:3700) >>> #5 0x7ffff5f412cc __libc_calloc(n=, >>> elem_size=) (malloc.c:3219) >>> #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) >>> #7 0x7ffff76b132a csoundAuxAlloc() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) >>> #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>> #10 0x7ffff76d636f process_score_event() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>> #12 0x7ffff782ffa8 csoundPerform() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #13 0x44f48e Csound::Perform(this=0x6fae90 ) >>> (csound/Csound6.05/include/csound.hpp:273) >>> >>> any ideas? >>> >>> Pete >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio

Date	2016-05-05 12:29
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	Hi Peter, I saw that the message says you are using Csound 6.05. Do you have access to a newer version of Csound? steven On Thu, May 5, 2016 at 7:19 AM, Peter Burgess wrote: > Ok, it does work.... and it's reporting 2389 errors... eek!!!!! > > On Thu, May 5, 2016 at 12:17 PM, Peter Burgess > wrote: >> I have got valgrind, but when I last tried to use it, it didn't seem >> to do anything.... having said that, I might of tried it the time I >> had an accidental infinate loop in my code somewhere, so it might of >> just been stuck on an infinite loop.... I'll give it another shot >> >> On Thu, May 5, 2016 at 12:15 PM, jpff wrote: >>> Do you hae access to valgrind? That is what I usually use to assist in >>> memory problems -- plus thinking of course. >>> ==John >>> >>> >>> >>> On Thu, 5 May 2016, Peter Burgess wrote: >>> >>>> Hi Csounders, I'm suddenly getting an error in my app today, and I'm >>>> struggling to track it down. It says this: >>>> >>>> * Error in >>>> `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': >>>> corrupted double-linked list: 0x0000000003e1cdf0 * >>>> Csound tidy up: Aborted >>>> >>>> It happens on about 70% of runs, and the only things I remember >>>> changing before it started was adding some EQ to my master out >>>> instrument definition, and changing some "=" to "init"... but I guess >>>> I must of done something else too, lol. >>>> >>>> I've debugged a few times, and it seems to happen in two different >>>> places during Csound performance, here are the stack traces from >>>> csoundPerform() on: >>>> >>>> Stack 1: >>>> >>>> #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #1 0x7ffff782e8fa kperf_nodebug() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #2 0x7ffff783004e csoundPerform() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #3 0x44f48e Csound::Perform(this=0x6fae90 ) >>>> (csound/Csound6.05/include/csound.hpp:273) >>>> >>>> Stack 2: >>>> >>>> #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) >>>> (../nptl/sysdeps/unix/sysv/linux/raise.c:56) >>>> #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) >>>> #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, >>>> fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") >>>> (../sysdeps/posix/libc_fatal.c:175) >>>> #3 0x7ffff5f3c0f7 malloc_printerr(action=, >>>> str=0x7ffff603bbfc "corrupted double-linked list", ptr=>>> out>) (malloc.c:4996) >>>> #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 >>>> , bytes=bytes@entry=80) (malloc.c:3700) >>>> #5 0x7ffff5f412cc __libc_calloc(n=, >>>> elem_size=) (malloc.c:3219) >>>> #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #7 0x7ffff76b132a csoundAuxAlloc() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #10 0x7ffff76d636f process_score_event() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #12 0x7ffff782ffa8 csoundPerform() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #13 0x44f48e Csound::Perform(this=0x6fae90 ) >>>> (csound/Csound6.05/include/csound.hpp:273) >>>> >>>> any ideas? >>>> >>>> Pete >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>>> >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 12:33
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	I'm not using 6.05, I'm on 6.07... but it would appear that I'm still linking to csound.hpp from 6.05. I didn't understand what I was doing with the libraries and header files when I started this project, and so I copied the whole of Csound into a folder in my project and linked to it there. Clearly I haven't changed that link since. I'll change that, and report back On Thu, May 5, 2016 at 12:29 PM, Steven Yi wrote: > Hi Peter, > > I saw that the message says you are using Csound 6.05. Do you have > access to a newer version of Csound? > > steven > > On Thu, May 5, 2016 at 7:19 AM, Peter Burgess > wrote: >> Ok, it does work.... and it's reporting 2389 errors... eek!!!!! >> >> On Thu, May 5, 2016 at 12:17 PM, Peter Burgess >> wrote: >>> I have got valgrind, but when I last tried to use it, it didn't seem >>> to do anything.... having said that, I might of tried it the time I >>> had an accidental infinate loop in my code somewhere, so it might of >>> just been stuck on an infinite loop.... I'll give it another shot >>> >>> On Thu, May 5, 2016 at 12:15 PM, jpff wrote: >>>> Do you hae access to valgrind? That is what I usually use to assist in >>>> memory problems -- plus thinking of course. >>>> ==John >>>> >>>> >>>> >>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>> >>>>> Hi Csounders, I'm suddenly getting an error in my app today, and I'm >>>>> struggling to track it down. It says this: >>>>> >>>>> * Error in >>>>> `/home/pete/Documents/AlgoRadioGUI/bin/Debug/AlgorythmRadioDebug': >>>>> corrupted double-linked list: 0x0000000003e1cdf0 * >>>>> Csound tidy up: Aborted >>>>> >>>>> It happens on about 70% of runs, and the only things I remember >>>>> changing before it started was adding some EQ to my master out >>>>> instrument definition, and changing some "=" to "init"... but I guess >>>>> I must of done something else too, lol. >>>>> >>>>> I've debugged a few times, and it seems to happen in two different >>>>> places during Csound performance, here are the stack traces from >>>>> csoundPerform() on: >>>>> >>>>> Stack 1: >>>>> >>>>> #0 0x7ffff76cd460 useropcd2() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #2 0x7ffff783004e csoundPerform() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #3 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>> >>>>> Stack 2: >>>>> >>>>> #0 0x7ffff5ef4cc9 __GI_raise(sig=sig@entry=6) >>>>> (../nptl/sysdeps/unix/sysv/linux/raise.c:56) >>>>> #1 0x7ffff5ef80d8 __GI_abort() (abort.c:89) >>>>> #2 0x7ffff5f31394 __libc_message(do_abort=do_abort@entry=1, >>>>> fmt=fmt@entry=0x7ffff603fb28 "* Error in `%s': %s: 0x%s *\n") >>>>> (../sysdeps/posix/libc_fatal.c:175) >>>>> #3 0x7ffff5f3c0f7 malloc_printerr(action=, >>>>> str=0x7ffff603bbfc "corrupted double-linked list", ptr=>>>> out>) (malloc.c:4996) >>>>> #4 0x7ffff5f3ef89 _int_malloc(av=av@entry=0x7ffff627c760 >>>>> , bytes=bytes@entry=80) (malloc.c:3700) >>>>> #5 0x7ffff5f412cc __libc_calloc(n=, >>>>> elem_size=) (malloc.c:3219) >>>>> #6 0x7ffff76d1091 mcalloc() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #7 0x7ffff76b132a csoundAuxAlloc() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #8 0x7ffff7744ea0 xsgset() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #9 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #10 0x7ffff76d636f process_score_event() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #11 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #12 0x7ffff782ffa8 csoundPerform() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #13 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>> >>>>> any ideas? >>>>> >>>>> Pete >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>>> >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 12:41
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	recompiled against the correct header, but no dice. I'll watch some valgrind tutorials and get a grip on what all it's messages mean. Btw, I just got an error with a different stack trace again (this was still linked to the old header): #0 0x7ffff76e68fe cs_hash_table_get() (/usr/local/lib/libcsound64.so.6.0:??) #1 0x7ffff76e54db csoundFindVariableWithName() (/usr/local/lib/libcsound64.so.6.0:??) #2 0x7ffff76ca8ce useropcdset() (/usr/local/lib/libcsound64.so.6.0:??) #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) #4 0x7ffff76d636f process_score_event() (/usr/local/lib/libcsound64.so.6.0:??) #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) #6 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) #7 0x44f48e Csound::Perform(this=0x6fae90 ) (csound/Csound6.05/include/csound.hpp:273) Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 12:46
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	Are you sure about the header? It still says: #7 0x44f48e Csound::Perform(this=0x6fae90 ) (csound/Csound6.05/include/csound.hpp:273) On Thu, May 5, 2016 at 7:41 AM, Peter Burgess wrote: > recompiled against the correct header, but no dice. I'll watch some > valgrind tutorials and get a grip on what all it's messages mean. Btw, > I just got an error with a different stack trace again (this was still > linked to the old header): > > #0 0x7ffff76e68fe cs_hash_table_get() (/usr/local/lib/libcsound64.so.6.0:??) > #1 0x7ffff76e54db csoundFindVariableWithName() > (/usr/local/lib/libcsound64.so.6.0:??) > #2 0x7ffff76ca8ce useropcdset() (/usr/local/lib/libcsound64.so.6.0:??) > #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) > #4 0x7ffff76d636f process_score_event() > (/usr/local/lib/libcsound64.so.6.0:??) > #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) > #6 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) > #7 0x44f48e Csound::Perform(this=0x6fae90 ) > (csound/Csound6.05/include/csound.hpp:273) > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 12:51
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Yes, that was from just before I changed the search path, this is a newer stack trace: #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) #1 0x7ffff782e8fa kperf_nodebug() (/usr/local/lib/libcsound64.so.6.0:??) #2 0x7ffff783004e csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) (/usr/local/include/csound/csound.hpp:276) Which I will point out is different again. Is it usual for an error to appear to happen in 4 or more different places? ps This might make you chuckle... Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost in loss record 5,511 of 5,512\| 15 MBs lost!!!! On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: > Are you sure about the header? It still says: > > #7 0x44f48e Csound::Perform(this=0x6fae90 ) > (csound/Csound6.05/include/csound.hpp:273) > > On Thu, May 5, 2016 at 7:41 AM, Peter Burgess > wrote: >> recompiled against the correct header, but no dice. I'll watch some >> valgrind tutorials and get a grip on what all it's messages mean. Btw, >> I just got an error with a different stack trace again (this was still >> linked to the old header): >> >> #0 0x7ffff76e68fe cs_hash_table_get() (/usr/local/lib/libcsound64.so.6.0:??) >> #1 0x7ffff76e54db csoundFindVariableWithName() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #2 0x7ffff76ca8ce useropcdset() (/usr/local/lib/libcsound64.so.6.0:??) >> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >> #4 0x7ffff76d636f process_score_event() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >> #6 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) >> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >> (csound/Csound6.05/include/csound.hpp:273) >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 13:00
From	jpff
Subject	Re: Seg fault - "corrupted double-linked list:"
	If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake you would get more information. On Thu, 5 May 2016, Peter Burgess wrote: > Yes, that was from just before I changed the search path, this is a > newer stack trace: > > #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) > #1 0x7ffff782e8fa kperf_nodebug() (/usr/local/lib/libcsound64.so.6.0:??) > #2 0x7ffff783004e csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) > #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) > (/usr/local/include/csound/csound.hpp:276) > > Which I will point out is different again. Is it usual for an error to > appear to happen in 4 or more different places? > > ps This might make you chuckle... > > Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost > in loss record 5,511 of 5,512\| > > 15 MBs lost!!!! > > On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >> Are you sure about the header? It still says: >> >> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >> (csound/Csound6.05/include/csound.hpp:273) >> >> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >> wrote: >>> recompiled against the correct header, but no dice. I'll watch some >>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>> I just got an error with a different stack trace again (this was still >>> linked to the old header): >>> >>> #0 0x7ffff76e68fe cs_hash_table_get() (/usr/local/lib/libcsound64.so.6.0:??) >>> #1 0x7ffff76e54db csoundFindVariableWithName() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #2 0x7ffff76ca8ce useropcdset() (/usr/local/lib/libcsound64.so.6.0:??) >>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>> #4 0x7ffff76d636f process_score_event() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>> #6 0x7ffff782ffa8 csoundPerform() (/usr/local/lib/libcsound64.so.6.0:??) >>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>> (csound/Csound6.05/include/csound.hpp:273) >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 13:04
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Huh, ok, if I struggle too long with malloc, I'll give that a shot. It seems to be complaining alot about uninitialised values in the code for my app. I'm not sure if that's the cause of this bug, cos the code it's refering to hasn't changed in months, but I guess I best follow it all through and see what happens anyway. On Thu, May 5, 2016 at 1:00 PM, jpff wrote: > If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake > you would get more information. > > On Thu, 5 May 2016, Peter Burgess wrote: > >> Yes, that was from just before I changed the search path, this is a >> newer stack trace: >> >> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >> #1 0x7ffff782e8fa kperf_nodebug() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #2 0x7ffff783004e csoundPerform() >> (/usr/local/lib/libcsound64.so.6.0:??) >> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >> (/usr/local/include/csound/csound.hpp:276) >> >> Which I will point out is different again. Is it usual for an error to >> appear to happen in 4 or more different places? >> >> ps This might make you chuckle... >> >> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >> in loss record 5,511 of 5,512\| >> >> 15 MBs lost!!!! >> >> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>> >>> Are you sure about the header? It still says: >>> >>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>> (csound/Csound6.05/include/csound.hpp:273) >>> >>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>> wrote: >>>> >>>> recompiled against the correct header, but no dice. I'll watch some >>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>> I just got an error with a different stack trace again (this was still >>>> linked to the old header): >>>> >>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #2 0x7ffff76ca8ce useropcdset() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #4 0x7ffff76d636f process_score_event() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #6 0x7ffff782ffa8 csoundPerform() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>> (csound/Csound6.05/include/csound.hpp:273) >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 13:05
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	*valgrind, not malloc On Thu, May 5, 2016 at 1:04 PM, Peter Burgess wrote: > Huh, ok, if I struggle too long with malloc, I'll give that a shot. It > seems to be complaining alot about uninitialised values in the code > for my app. I'm not sure if that's the cause of this bug, cos the code > it's refering to hasn't changed in months, but I guess I best follow > it all through and see what happens anyway. > > On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >> you would get more information. >> >> On Thu, 5 May 2016, Peter Burgess wrote: >> >>> Yes, that was from just before I changed the search path, this is a >>> newer stack trace: >>> >>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>> #1 0x7ffff782e8fa kperf_nodebug() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #2 0x7ffff783004e csoundPerform() >>> (/usr/local/lib/libcsound64.so.6.0:??) >>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>> (/usr/local/include/csound/csound.hpp:276) >>> >>> Which I will point out is different again. Is it usual for an error to >>> appear to happen in 4 or more different places? >>> >>> ps This might make you chuckle... >>> >>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>> in loss record 5,511 of 5,512\| >>> >>> 15 MBs lost!!!! >>> >>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>> >>>> Are you sure about the header? It still says: >>>> >>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>> (csound/Csound6.05/include/csound.hpp:273) >>>> >>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>> wrote: >>>>> >>>>> recompiled against the correct header, but no dice. I'll watch some >>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>> I just got an error with a different stack trace again (this was still >>>>> linked to the old header): >>>>> >>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #2 0x7ffff76ca8ce useropcdset() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #4 0x7ffff76d636f process_score_event() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio

Date	2016-05-05 13:24
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	I'm not sure how your program works, but if it generates a CSD to play, you could post the CSD and one of us can test with it. On Thu, May 5, 2016 at 8:05 AM, Peter Burgess wrote: > *valgrind, not malloc > > On Thu, May 5, 2016 at 1:04 PM, Peter Burgess > wrote: >> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >> seems to be complaining alot about uninitialised values in the code >> for my app. I'm not sure if that's the cause of this bug, cos the code >> it's refering to hasn't changed in months, but I guess I best follow >> it all through and see what happens anyway. >> >> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>> you would get more information. >>> >>> On Thu, 5 May 2016, Peter Burgess wrote: >>> >>>> Yes, that was from just before I changed the search path, this is a >>>> newer stack trace: >>>> >>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>> #1 0x7ffff782e8fa kperf_nodebug() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #2 0x7ffff783004e csoundPerform() >>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>> (/usr/local/include/csound/csound.hpp:276) >>>> >>>> Which I will point out is different again. Is it usual for an error to >>>> appear to happen in 4 or more different places? >>>> >>>> ps This might make you chuckle... >>>> >>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>> in loss record 5,511 of 5,512\| >>>> >>>> 15 MBs lost!!!! >>>> >>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>> >>>>> Are you sure about the header? It still says: >>>>> >>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>> >>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>> wrote: >>>>>> >>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>> I just got an error with a different stack trace again (this was still >>>>>> linked to the old header): >>>>>> >>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #4 0x7ffff76d636f process_score_event() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>>> >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 13:26
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	That's a good point, I already have it printing the csds and scores for debug purposes. I'll find one that throws up an error shortly... On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: > I'm not sure how your program works, but if it generates a CSD to > play, you could post the CSD and one of us can test with it. > > On Thu, May 5, 2016 at 8:05 AM, Peter Burgess > wrote: >> *valgrind, not malloc >> >> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >> wrote: >>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>> seems to be complaining alot about uninitialised values in the code >>> for my app. I'm not sure if that's the cause of this bug, cos the code >>> it's refering to hasn't changed in months, but I guess I best follow >>> it all through and see what happens anyway. >>> >>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>> you would get more information. >>>> >>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>> >>>>> Yes, that was from just before I changed the search path, this is a >>>>> newer stack trace: >>>>> >>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #2 0x7ffff783004e csoundPerform() >>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>> (/usr/local/include/csound/csound.hpp:276) >>>>> >>>>> Which I will point out is different again. Is it usual for an error to >>>>> appear to happen in 4 or more different places? >>>>> >>>>> ps This might make you chuckle... >>>>> >>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>> in loss record 5,511 of 5,512\| >>>>> >>>>> 15 MBs lost!!!! >>>>> >>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>> >>>>>> Are you sure about the header? It still says: >>>>>> >>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>> >>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>> wrote: >>>>>>> >>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>> I just got an error with a different stack trace again (this was still >>>>>>> linked to the old header): >>>>>>> >>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>>> >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 13:38
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
Attachments	debug.csd
	Ok, it's not much to look at by eye, but this threw up the same seg fault. I've tried them in CsoundQT, and its giving me a segfault there too. It sounds disgusting and has samples out of range (something gone seriously skewif with the mastering!!!), so turn your speakers, and I appologise for the gabbaish sounding music :) On Thu, May 5, 2016 at 1:26 PM, Peter Burgess wrote: > That's a good point, I already have it printing the csds and scores > for debug purposes. I'll find one that throws up an error shortly... > > On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >> I'm not sure how your program works, but if it generates a CSD to >> play, you could post the CSD and one of us can test with it. >> >> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >> wrote: >>> *valgrind, not malloc >>> >>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>> wrote: >>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>> seems to be complaining alot about uninitialised values in the code >>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>> it's refering to hasn't changed in months, but I guess I best follow >>>> it all through and see what happens anyway. >>>> >>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>> you would get more information. >>>>> >>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>> >>>>>> Yes, that was from just before I changed the search path, this is a >>>>>> newer stack trace: >>>>>> >>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #2 0x7ffff783004e csoundPerform() >>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>> >>>>>> Which I will point out is different again. Is it usual for an error to >>>>>> appear to happen in 4 or more different places? >>>>>> >>>>>> ps This might make you chuckle... >>>>>> >>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>> in loss record 5,511 of 5,512\| >>>>>> >>>>>> 15 MBs lost!!!! >>>>>> >>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>> >>>>>>> Are you sure about the header? It still says: >>>>>>> >>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>> >>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>> wrote: >>>>>>>> >>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>> linked to the old header): >>>>>>>> >>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio -- http://algorythmradio.com https://soundcloud.com/algorythmradio Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 14:00
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	I'm unable to run this project as it looks like it's using a custom opcode "tableWobbleS_N". Is that the case? On Thu, May 5, 2016 at 8:38 AM, Peter Burgess wrote: > Ok, it's not much to look at by eye, but this threw up the same seg > fault. I've tried them in CsoundQT, and its giving me a segfault there > too. It sounds disgusting and has samples out of range (something gone > seriously skewif with the mastering!!!), so turn your speakers, and I > appologise for the gabbaish sounding music :) > > > > > > On Thu, May 5, 2016 at 1:26 PM, Peter Burgess > wrote: >> That's a good point, I already have it printing the csds and scores >> for debug purposes. I'll find one that throws up an error shortly... >> >> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>> I'm not sure how your program works, but if it generates a CSD to >>> play, you could post the CSD and one of us can test with it. >>> >>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>> wrote: >>>> *valgrind, not malloc >>>> >>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>> wrote: >>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>> seems to be complaining alot about uninitialised values in the code >>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>> it all through and see what happens anyway. >>>>> >>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>> you would get more information. >>>>>> >>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>> >>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>> newer stack trace: >>>>>>> >>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>> >>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>> appear to happen in 4 or more different places? >>>>>>> >>>>>>> ps This might make you chuckle... >>>>>>> >>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>> in loss record 5,511 of 5,512\| >>>>>>> >>>>>>> 15 MBs lost!!!! >>>>>>> >>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>> >>>>>>>> Are you sure about the header? It still says: >>>>>>>> >>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>> linked to the old header): >>>>>>>>> >>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 14:24
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	ah right yeah...what platform you on? I've compiled it on 64bit linux, otherwise I'd have to send you the source. As a side note, when I get round to writing the description and example, I'm gonna submit that opcode to you guys to see if you'll add it to csound On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: > I'm unable to run this project as it looks like it's using a custom > opcode "tableWobbleS_N". Is that the case? > > On Thu, May 5, 2016 at 8:38 AM, Peter Burgess > wrote: >> Ok, it's not much to look at by eye, but this threw up the same seg >> fault. I've tried them in CsoundQT, and its giving me a segfault there >> too. It sounds disgusting and has samples out of range (something gone >> seriously skewif with the mastering!!!), so turn your speakers, and I >> appologise for the gabbaish sounding music :) >> >> >> >> >> >> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >> wrote: >>> That's a good point, I already have it printing the csds and scores >>> for debug purposes. I'll find one that throws up an error shortly... >>> >>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>> I'm not sure how your program works, but if it generates a CSD to >>>> play, you could post the CSD and one of us can test with it. >>>> >>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>> wrote: >>>>> *valgrind, not malloc >>>>> >>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>> wrote: >>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>> seems to be complaining alot about uninitialised values in the code >>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>> it all through and see what happens anyway. >>>>>> >>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>> you would get more information. >>>>>>> >>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>> >>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>> newer stack trace: >>>>>>>> >>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>> >>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>> appear to happen in 4 or more different places? >>>>>>>> >>>>>>>> ps This might make you chuckle... >>>>>>>> >>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>> >>>>>>>> 15 MBs lost!!!! >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>> >>>>>>>>> Are you sure about the header? It still says: >>>>>>>>> >>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>> linked to the old header): >>>>>>>>>> >>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 14:26
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Or I could remove that opcode and see if it still segfaults On Thu, May 5, 2016 at 2:24 PM, Peter Burgess wrote: > ah right yeah...what platform you on? I've compiled it on 64bit linux, > otherwise I'd have to send you the source. > > As a side note, when I get round to writing the description and > example, I'm gonna submit that opcode to you guys to see if you'll add > it to csound > > On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >> I'm unable to run this project as it looks like it's using a custom >> opcode "tableWobbleS_N". Is that the case? >> >> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >> wrote: >>> Ok, it's not much to look at by eye, but this threw up the same seg >>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>> too. It sounds disgusting and has samples out of range (something gone >>> seriously skewif with the mastering!!!), so turn your speakers, and I >>> appologise for the gabbaish sounding music :) >>> >>> >>> >>> >>> >>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>> wrote: >>>> That's a good point, I already have it printing the csds and scores >>>> for debug purposes. I'll find one that throws up an error shortly... >>>> >>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>> I'm not sure how your program works, but if it generates a CSD to >>>>> play, you could post the CSD and one of us can test with it. >>>>> >>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>> wrote: >>>>>> *valgrind, not malloc >>>>>> >>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>> wrote: >>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>> it all through and see what happens anyway. >>>>>>> >>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>> you would get more information. >>>>>>>> >>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>> >>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>> newer stack trace: >>>>>>>>> >>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>> >>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>> >>>>>>>>> ps This might make you chuckle... >>>>>>>>> >>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>> >>>>>>>>> 15 MBs lost!!!! >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>> >>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>> >>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>> linked to the old header): >>>>>>>>>>> >>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio

Date	2016-05-05 14:27
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	I would try removing the opcode first. If the problem goes away, that'd certainly narrow the scope of where to look. If the problem persists, you could post the opcode code here or somewhere online to download from. I'm on Windows primarily, but I have access to Linux and OSX computers and VM's. On Thu, May 5, 2016 at 9:26 AM, Peter Burgess wrote: > Or I could remove that opcode and see if it still segfaults > > On Thu, May 5, 2016 at 2:24 PM, Peter Burgess > wrote: >> ah right yeah...what platform you on? I've compiled it on 64bit linux, >> otherwise I'd have to send you the source. >> >> As a side note, when I get round to writing the description and >> example, I'm gonna submit that opcode to you guys to see if you'll add >> it to csound >> >> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>> I'm unable to run this project as it looks like it's using a custom >>> opcode "tableWobbleS_N". Is that the case? >>> >>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>> wrote: >>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>> too. It sounds disgusting and has samples out of range (something gone >>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>> appologise for the gabbaish sounding music :) >>>> >>>> >>>> >>>> >>>> >>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>> wrote: >>>>> That's a good point, I already have it printing the csds and scores >>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>> >>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>> play, you could post the CSD and one of us can test with it. >>>>>> >>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>> wrote: >>>>>>> *valgrind, not malloc >>>>>>> >>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>> wrote: >>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>> it all through and see what happens anyway. >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>> you would get more information. >>>>>>>>> >>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>> >>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>> newer stack trace: >>>>>>>>>> >>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>> >>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>> >>>>>>>>>> ps This might make you chuckle... >>>>>>>>>> >>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>> >>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>> >>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>> >>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>> linked to the old header): >>>>>>>>>>>> >>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 14:31
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
Attachments	debug.csd
	Ok, here it is: On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: > I would try removing the opcode first. If the problem goes away, > that'd certainly narrow the scope of where to look. If the problem > persists, you could post the opcode code here or somewhere online to > download from. I'm on Windows primarily, but I have access to Linux > and OSX computers and VM's. > > On Thu, May 5, 2016 at 9:26 AM, Peter Burgess > wrote: >> Or I could remove that opcode and see if it still segfaults >> >> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >> wrote: >>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>> otherwise I'd have to send you the source. >>> >>> As a side note, when I get round to writing the description and >>> example, I'm gonna submit that opcode to you guys to see if you'll add >>> it to csound >>> >>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>> I'm unable to run this project as it looks like it's using a custom >>>> opcode "tableWobbleS_N". Is that the case? >>>> >>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>> wrote: >>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>> too. It sounds disgusting and has samples out of range (something gone >>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>> appologise for the gabbaish sounding music :) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>> wrote: >>>>>> That's a good point, I already have it printing the csds and scores >>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>> >>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>> >>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>> wrote: >>>>>>>> *valgrind, not malloc >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>> it all through and see what happens anyway. >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>> you would get more information. >>>>>>>>>> >>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>> >>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>> newer stack trace: >>>>>>>>>>> >>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>> >>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>> >>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>> >>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>> >>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>> >>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>> >>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>> >>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here -- http://algorythmradio.com https://soundcloud.com/algorythmradio Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 14:44
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	I get different results here (crashes). If rendering to dac I get: 0x000000006c778f5d in pthread_mutex_trylock () from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll (gdb) bt #0 0x000000006c778f5d in pthread_mutex_trylock () from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, milliseconds=500) at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, nbytes=) at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 #3 0x000000006c52311e in spoutsf (csound=0x2460080) at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 If rendering to disk I get: Thread 1 received signal SIGSEGV, Segmentation fault. kperf_nodebug (csound=0x25d0080) at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 1589 opstart->insdshead->pds = opstart; (gdb) bt #0 kperf_nodebug (csound=0x25d0080) at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 This is on Windows 64bit. I've got to tend to other things at the moment but I will take another look again later. Perhaps others will give your CSD a try as well. On Thu, May 5, 2016 at 9:31 AM, Peter Burgess wrote: > Ok, here it is: > > On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >> I would try removing the opcode first. If the problem goes away, >> that'd certainly narrow the scope of where to look. If the problem >> persists, you could post the opcode code here or somewhere online to >> download from. I'm on Windows primarily, but I have access to Linux >> and OSX computers and VM's. >> >> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >> wrote: >>> Or I could remove that opcode and see if it still segfaults >>> >>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>> wrote: >>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>> otherwise I'd have to send you the source. >>>> >>>> As a side note, when I get round to writing the description and >>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>> it to csound >>>> >>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>> I'm unable to run this project as it looks like it's using a custom >>>>> opcode "tableWobbleS_N". Is that the case? >>>>> >>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>> wrote: >>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>> appologise for the gabbaish sounding music :) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>> wrote: >>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>> >>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> *valgrind, not malloc >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>> you would get more information. >>>>>>>>>>> >>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>> >>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>> newer stack trace: >>>>>>>>>>>> >>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>> >>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>> >>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>> >>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>> >>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>> >>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>> >>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 14:47
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Cheers for having a look! In my app, I've only been exporting to disk, but in both cases it looks like it must be a similar reason for the crash. Seeing as I've got a faulty csd file, I should go through it and see if I can narrow down where the problem is. Should of thought of that earlier! :D On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: > I get different results here (crashes). If rendering to dac I get: > > 0x000000006c778f5d in pthread_mutex_trylock () > from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll > (gdb) bt > #0 0x000000006c778f5d in pthread_mutex_trylock () > from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll > #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, > milliseconds=500) > at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 > #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, > nbytes=) > at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 > #3 0x000000006c52311e in spoutsf (csound=0x2460080) > at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 > #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) > at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 > #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) > at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 > #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) > at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 > > If rendering to disk I get: > > Thread 1 received signal SIGSEGV, Segmentation fault. > kperf_nodebug (csound=0x25d0080) > at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 > 1589 opstart->insdshead->pds = opstart; > (gdb) bt > #0 kperf_nodebug (csound=0x25d0080) > at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 > #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) > at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 > #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) > at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 > > This is on Windows 64bit. I've got to tend to other things at the > moment but I will take another look again later. Perhaps others will > give your CSD a try as well. > > On Thu, May 5, 2016 at 9:31 AM, Peter Burgess > wrote: >> Ok, here it is: >> >> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>> I would try removing the opcode first. If the problem goes away, >>> that'd certainly narrow the scope of where to look. If the problem >>> persists, you could post the opcode code here or somewhere online to >>> download from. I'm on Windows primarily, but I have access to Linux >>> and OSX computers and VM's. >>> >>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>> wrote: >>>> Or I could remove that opcode and see if it still segfaults >>>> >>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>> wrote: >>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>> otherwise I'd have to send you the source. >>>>> >>>>> As a side note, when I get round to writing the description and >>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>> it to csound >>>>> >>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>> >>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>> wrote: >>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>> appologise for the gabbaish sounding music :) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>> wrote: >>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> *valgrind, not malloc >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>> wrote: >>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>> you would get more information. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>> >>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>> >>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>> >>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>> >>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>> >>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>> >>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 14:58
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Ah, I've found the offending article! Sorry about the wild goose chase. I'm accidently using 0 as a delay time in multitap. One of the pitfalls of random instrument generation I guess :D Is this the kind of thing that would have gotten picked up if I'd built csound with debug mode? On Thu, May 5, 2016 at 2:47 PM, Peter Burgess wrote: > Cheers for having a look! In my app, I've only been exporting to disk, > but in both cases it looks like it must be a similar reason for the > crash. Seeing as I've got a faulty csd file, I should go through it > and see if I can narrow down where the problem is. Should of thought > of that earlier! :D > > On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: >> I get different results here (crashes). If rendering to dac I get: >> >> 0x000000006c778f5d in pthread_mutex_trylock () >> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >> (gdb) bt >> #0 0x000000006c778f5d in pthread_mutex_trylock () >> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >> #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, >> milliseconds=500) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 >> #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, >> nbytes=) >> at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 >> #3 0x000000006c52311e in spoutsf (csound=0x2460080) >> at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 >> #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 >> #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >> #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) >> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >> >> If rendering to disk I get: >> >> Thread 1 received signal SIGSEGV, Segmentation fault. >> kperf_nodebug (csound=0x25d0080) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >> 1589 opstart->insdshead->pds = opstart; >> (gdb) bt >> #0 kperf_nodebug (csound=0x25d0080) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >> #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) >> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >> #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) >> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >> >> This is on Windows 64bit. I've got to tend to other things at the >> moment but I will take another look again later. Perhaps others will >> give your CSD a try as well. >> >> On Thu, May 5, 2016 at 9:31 AM, Peter Burgess >> wrote: >>> Ok, here it is: >>> >>> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>>> I would try removing the opcode first. If the problem goes away, >>>> that'd certainly narrow the scope of where to look. If the problem >>>> persists, you could post the opcode code here or somewhere online to >>>> download from. I'm on Windows primarily, but I have access to Linux >>>> and OSX computers and VM's. >>>> >>>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>>> wrote: >>>>> Or I could remove that opcode and see if it still segfaults >>>>> >>>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>>> wrote: >>>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>>> otherwise I'd have to send you the source. >>>>>> >>>>>> As a side note, when I get round to writing the description and >>>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>>> it to csound >>>>>> >>>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>>> >>>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>>> wrote: >>>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>>> appologise for the gabbaish sounding music :) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>>> wrote: >>>>>>>>>>> *valgrind, not malloc >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>>> wrote: >>>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>>> you would get more information. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>>> >>>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>>> >>>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>>> >>>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>>> >>>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio

Date	2016-05-05 15:09
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	Oh wow, glad you found the issue. I'm not sure this would have been found in debug mode. It could be a case where we need to do some kind of check and provide a more graceful exit condition by just turning off the instrument. Could you file an issue about this? On Thu, May 5, 2016 at 9:58 AM, Peter Burgess wrote: > Ah, I've found the offending article! Sorry about the wild goose > chase. I'm accidently using 0 as a delay time in multitap. One of the > pitfalls of random instrument generation I guess :D Is this the kind > of thing that would have gotten picked up if I'd built csound with > debug mode? > > On Thu, May 5, 2016 at 2:47 PM, Peter Burgess > wrote: >> Cheers for having a look! In my app, I've only been exporting to disk, >> but in both cases it looks like it must be a similar reason for the >> crash. Seeing as I've got a faulty csd file, I should go through it >> and see if I can narrow down where the problem is. Should of thought >> of that earlier! :D >> >> On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: >>> I get different results here (crashes). If rendering to dac I get: >>> >>> 0x000000006c778f5d in pthread_mutex_trylock () >>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>> (gdb) bt >>> #0 0x000000006c778f5d in pthread_mutex_trylock () >>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>> #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, >>> milliseconds=500) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 >>> #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, >>> nbytes=) >>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 >>> #3 0x000000006c52311e in spoutsf (csound=0x2460080) >>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 >>> #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 >>> #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>> #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) >>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>> >>> If rendering to disk I get: >>> >>> Thread 1 received signal SIGSEGV, Segmentation fault. >>> kperf_nodebug (csound=0x25d0080) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>> 1589 opstart->insdshead->pds = opstart; >>> (gdb) bt >>> #0 kperf_nodebug (csound=0x25d0080) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>> #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) >>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>> #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) >>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>> >>> This is on Windows 64bit. I've got to tend to other things at the >>> moment but I will take another look again later. Perhaps others will >>> give your CSD a try as well. >>> >>> On Thu, May 5, 2016 at 9:31 AM, Peter Burgess >>> wrote: >>>> Ok, here it is: >>>> >>>> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>>>> I would try removing the opcode first. If the problem goes away, >>>>> that'd certainly narrow the scope of where to look. If the problem >>>>> persists, you could post the opcode code here or somewhere online to >>>>> download from. I'm on Windows primarily, but I have access to Linux >>>>> and OSX computers and VM's. >>>>> >>>>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>>>> wrote: >>>>>> Or I could remove that opcode and see if it still segfaults >>>>>> >>>>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>>>> wrote: >>>>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>>>> otherwise I'd have to send you the source. >>>>>>> >>>>>>> As a side note, when I get round to writing the description and >>>>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>>>> it to csound >>>>>>> >>>>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>>>> appologise for the gabbaish sounding music :) >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>>>> wrote: >>>>>>>>>>>> *valgrind, not malloc >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>>>> wrote: >>>>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>>>> you would get more information. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 15:29
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	I can, I've not filed an issue before, I usually just wine at you guys here ;) where do I do it? On Thu, May 5, 2016 at 3:09 PM, Steven Yi wrote: > Oh wow, glad you found the issue. I'm not sure this would have been > found in debug mode. It could be a case where we need to do some kind > of check and provide a more graceful exit condition by just turning > off the instrument. Could you file an issue about this? > > On Thu, May 5, 2016 at 9:58 AM, Peter Burgess > wrote: >> Ah, I've found the offending article! Sorry about the wild goose >> chase. I'm accidently using 0 as a delay time in multitap. One of the >> pitfalls of random instrument generation I guess :D Is this the kind >> of thing that would have gotten picked up if I'd built csound with >> debug mode? >> >> On Thu, May 5, 2016 at 2:47 PM, Peter Burgess >> wrote: >>> Cheers for having a look! In my app, I've only been exporting to disk, >>> but in both cases it looks like it must be a similar reason for the >>> crash. Seeing as I've got a faulty csd file, I should go through it >>> and see if I can narrow down where the problem is. Should of thought >>> of that earlier! :D >>> >>> On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: >>>> I get different results here (crashes). If rendering to dac I get: >>>> >>>> 0x000000006c778f5d in pthread_mutex_trylock () >>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>> (gdb) bt >>>> #0 0x000000006c778f5d in pthread_mutex_trylock () >>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>> #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, >>>> milliseconds=500) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 >>>> #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, >>>> nbytes=) >>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 >>>> #3 0x000000006c52311e in spoutsf (csound=0x2460080) >>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 >>>> #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 >>>> #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>> #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) >>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>> >>>> If rendering to disk I get: >>>> >>>> Thread 1 received signal SIGSEGV, Segmentation fault. >>>> kperf_nodebug (csound=0x25d0080) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>> 1589 opstart->insdshead->pds = opstart; >>>> (gdb) bt >>>> #0 kperf_nodebug (csound=0x25d0080) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>> #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) >>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>> #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) >>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>> >>>> This is on Windows 64bit. I've got to tend to other things at the >>>> moment but I will take another look again later. Perhaps others will >>>> give your CSD a try as well. >>>> >>>> On Thu, May 5, 2016 at 9:31 AM, Peter Burgess >>>> wrote: >>>>> Ok, here it is: >>>>> >>>>> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>>>>> I would try removing the opcode first. If the problem goes away, >>>>>> that'd certainly narrow the scope of where to look. If the problem >>>>>> persists, you could post the opcode code here or somewhere online to >>>>>> download from. I'm on Windows primarily, but I have access to Linux >>>>>> and OSX computers and VM's. >>>>>> >>>>>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>>>>> wrote: >>>>>>> Or I could remove that opcode and see if it still segfaults >>>>>>> >>>>>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>>>>> wrote: >>>>>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>>>>> otherwise I'd have to send you the source. >>>>>>>> >>>>>>>> As a side note, when I get round to writing the description and >>>>>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>>>>> it to csound >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>>>>> appologise for the gabbaish sounding music :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>>>>> wrote: >>>>>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>>>>> wrote: >>>>>>>>>>>>> *valgrind, not malloc >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>>>>> you would get more information. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here

Date	2016-05-05 15:42
From	Steven Yi
Subject	Re: Seg fault - "corrupted double-linked list:"
	The place to send bug reports is actually attached to each email on the Csound list :) Send bugs reports to https://github.com/csound/csound/issues On Thu, May 5, 2016 at 10:29 AM, Peter Burgess wrote: > I can, I've not filed an issue before, I usually just wine at you guys > here ;) where do I do it? > > On Thu, May 5, 2016 at 3:09 PM, Steven Yi wrote: >> Oh wow, glad you found the issue. I'm not sure this would have been >> found in debug mode. It could be a case where we need to do some kind >> of check and provide a more graceful exit condition by just turning >> off the instrument. Could you file an issue about this? >> >> On Thu, May 5, 2016 at 9:58 AM, Peter Burgess >> wrote: >>> Ah, I've found the offending article! Sorry about the wild goose >>> chase. I'm accidently using 0 as a delay time in multitap. One of the >>> pitfalls of random instrument generation I guess :D Is this the kind >>> of thing that would have gotten picked up if I'd built csound with >>> debug mode? >>> >>> On Thu, May 5, 2016 at 2:47 PM, Peter Burgess >>> wrote: >>>> Cheers for having a look! In my app, I've only been exporting to disk, >>>> but in both cases it looks like it must be a similar reason for the >>>> crash. Seeing as I've got a faulty csd file, I should go through it >>>> and see if I can narrow down where the problem is. Should of thought >>>> of that earlier! :D >>>> >>>> On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: >>>>> I get different results here (crashes). If rendering to dac I get: >>>>> >>>>> 0x000000006c778f5d in pthread_mutex_trylock () >>>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>>> (gdb) bt >>>>> #0 0x000000006c778f5d in pthread_mutex_trylock () >>>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>>> #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, >>>>> milliseconds=500) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 >>>>> #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, >>>>> nbytes=) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 >>>>> #3 0x000000006c52311e in spoutsf (csound=0x2460080) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 >>>>> #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 >>>>> #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>>> #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>>> >>>>> If rendering to disk I get: >>>>> >>>>> Thread 1 received signal SIGSEGV, Segmentation fault. >>>>> kperf_nodebug (csound=0x25d0080) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>>> 1589 opstart->insdshead->pds = opstart; >>>>> (gdb) bt >>>>> #0 kperf_nodebug (csound=0x25d0080) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>>> #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>>> #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) >>>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>>> >>>>> This is on Windows 64bit. I've got to tend to other things at the >>>>> moment but I will take another look again later. Perhaps others will >>>>> give your CSD a try as well. >>>>> >>>>> On Thu, May 5, 2016 at 9:31 AM, Peter Burgess >>>>> wrote: >>>>>> Ok, here it is: >>>>>> >>>>>> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>>>>>> I would try removing the opcode first. If the problem goes away, >>>>>>> that'd certainly narrow the scope of where to look. If the problem >>>>>>> persists, you could post the opcode code here or somewhere online to >>>>>>> download from. I'm on Windows primarily, but I have access to Linux >>>>>>> and OSX computers and VM's. >>>>>>> >>>>>>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>>>>>> wrote: >>>>>>>> Or I could remove that opcode and see if it still segfaults >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>>>>>> otherwise I'd have to send you the source. >>>>>>>>> >>>>>>>>> As a side note, when I get round to writing the description and >>>>>>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>>>>>> it to csound >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>>>>>> wrote: >>>>>>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>>>>>> appologise for the gabbaish sounding music :) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>>>>>> wrote: >>>>>>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> *valgrind, not malloc >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>>>>>> you would get more information. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> http://algorythmradio.com >>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://algorythmradio.com >>>>>> https://soundcloud.com/algorythmradio >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>> >>> >>> >>> -- >>> http://algorythmradio.com >>> https://soundcloud.com/algorythmradio >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > > -- > http://algorythmradio.com > https://soundcloud.com/algorythmradio > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-05 16:32
From	Peter Burgess
Subject	Re: Seg fault - "corrupted double-linked list:"
	Ah right, haha! I'll do that then On Thu, May 5, 2016 at 3:42 PM, Steven Yi wrote: > The place to send bug reports is actually attached to each email on > the Csound list :) > > Send bugs reports to > https://github.com/csound/csound/issues > > On Thu, May 5, 2016 at 10:29 AM, Peter Burgess > wrote: >> I can, I've not filed an issue before, I usually just wine at you guys >> here ;) where do I do it? >> >> On Thu, May 5, 2016 at 3:09 PM, Steven Yi wrote: >>> Oh wow, glad you found the issue. I'm not sure this would have been >>> found in debug mode. It could be a case where we need to do some kind >>> of check and provide a more graceful exit condition by just turning >>> off the instrument. Could you file an issue about this? >>> >>> On Thu, May 5, 2016 at 9:58 AM, Peter Burgess >>> wrote: >>>> Ah, I've found the offending article! Sorry about the wild goose >>>> chase. I'm accidently using 0 as a delay time in multitap. One of the >>>> pitfalls of random instrument generation I guess :D Is this the kind >>>> of thing that would have gotten picked up if I'd built csound with >>>> debug mode? >>>> >>>> On Thu, May 5, 2016 at 2:47 PM, Peter Burgess >>>> wrote: >>>>> Cheers for having a look! In my app, I've only been exporting to disk, >>>>> but in both cases it looks like it must be a similar reason for the >>>>> crash. Seeing as I've got a faulty csd file, I should go through it >>>>> and see if I can narrow down where the problem is. Should of thought >>>>> of that earlier! :D >>>>> >>>>> On Thu, May 5, 2016 at 2:44 PM, Steven Yi wrote: >>>>>> I get different results here (crashes). If rendering to dac I get: >>>>>> >>>>>> 0x000000006c778f5d in pthread_mutex_trylock () >>>>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>>>> (gdb) bt >>>>>> #0 0x000000006c778f5d in pthread_mutex_trylock () >>>>>> from C:\msys64\home\stevenyi\work\csound\csound\mingw64\csound-mingw64\csound64.dll >>>>>> #1 0x000000006c5fcef2 in csoundWaitThreadLock (lock=0x3ead4d0, >>>>>> milliseconds=500) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/threads.c:233 >>>>>> #2 0x0000000066e41536 in rtplay_ (csound=0x2460080, buffer=0x3ed7fb0, >>>>>> nbytes=) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/rtpa.c:526 >>>>>> #3 0x000000006c52311e in spoutsf (csound=0x2460080) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/InOut/libsnd.c:105 >>>>>> #4 0x000000006c5f638c in kperf_nodebug (csound=0x2460080) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1609 >>>>>> #5 0x000000006c5f7a7b in csoundPerform (csound=0xe) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>>>> #6 0x00000000004031e7 in main (argc=2, argv=0xec4710) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>>>> >>>>>> If rendering to disk I get: >>>>>> >>>>>> Thread 1 received signal SIGSEGV, Segmentation fault. >>>>>> kperf_nodebug (csound=0x25d0080) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>>>> 1589 opstart->insdshead->pds = opstart; >>>>>> (gdb) bt >>>>>> #0 kperf_nodebug (csound=0x25d0080) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:1589 >>>>>> #1 0x000000006c5f7a7b in csoundPerform (csound=0x9) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/Top/csound.c:2051 >>>>>> #2 0x00000000004031e7 in main (argc=4, argv=0xea4730) >>>>>> at C:/msys64/home/stevenyi/work/csound/csound/frontends/csound/csound_main.c:318 >>>>>> >>>>>> This is on Windows 64bit. I've got to tend to other things at the >>>>>> moment but I will take another look again later. Perhaps others will >>>>>> give your CSD a try as well. >>>>>> >>>>>> On Thu, May 5, 2016 at 9:31 AM, Peter Burgess >>>>>> wrote: >>>>>>> Ok, here it is: >>>>>>> >>>>>>> On Thu, May 5, 2016 at 2:27 PM, Steven Yi wrote: >>>>>>>> I would try removing the opcode first. If the problem goes away, >>>>>>>> that'd certainly narrow the scope of where to look. If the problem >>>>>>>> persists, you could post the opcode code here or somewhere online to >>>>>>>> download from. I'm on Windows primarily, but I have access to Linux >>>>>>>> and OSX computers and VM's. >>>>>>>> >>>>>>>> On Thu, May 5, 2016 at 9:26 AM, Peter Burgess >>>>>>>> wrote: >>>>>>>>> Or I could remove that opcode and see if it still segfaults >>>>>>>>> >>>>>>>>> On Thu, May 5, 2016 at 2:24 PM, Peter Burgess >>>>>>>>> wrote: >>>>>>>>>> ah right yeah...what platform you on? I've compiled it on 64bit linux, >>>>>>>>>> otherwise I'd have to send you the source. >>>>>>>>>> >>>>>>>>>> As a side note, when I get round to writing the description and >>>>>>>>>> example, I'm gonna submit that opcode to you guys to see if you'll add >>>>>>>>>> it to csound >>>>>>>>>> >>>>>>>>>> On Thu, May 5, 2016 at 2:00 PM, Steven Yi wrote: >>>>>>>>>>> I'm unable to run this project as it looks like it's using a custom >>>>>>>>>>> opcode "tableWobbleS_N". Is that the case? >>>>>>>>>>> >>>>>>>>>>> On Thu, May 5, 2016 at 8:38 AM, Peter Burgess >>>>>>>>>>> wrote: >>>>>>>>>>>> Ok, it's not much to look at by eye, but this threw up the same seg >>>>>>>>>>>> fault. I've tried them in CsoundQT, and its giving me a segfault there >>>>>>>>>>>> too. It sounds disgusting and has samples out of range (something gone >>>>>>>>>>>> seriously skewif with the mastering!!!), so turn your speakers, and I >>>>>>>>>>>> appologise for the gabbaish sounding music :) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 5, 2016 at 1:26 PM, Peter Burgess >>>>>>>>>>>> wrote: >>>>>>>>>>>>> That's a good point, I already have it printing the csds and scores >>>>>>>>>>>>> for debug purposes. I'll find one that throws up an error shortly... >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 5, 2016 at 1:24 PM, Steven Yi wrote: >>>>>>>>>>>>>> I'm not sure how your program works, but if it generates a CSD to >>>>>>>>>>>>>> play, you could post the CSD and one of us can test with it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 5, 2016 at 8:05 AM, Peter Burgess >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> *valgrind, not malloc >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 5, 2016 at 1:04 PM, Peter Burgess >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> Huh, ok, if I struggle too long with malloc, I'll give that a shot. It >>>>>>>>>>>>>>>> seems to be complaining alot about uninitialised values in the code >>>>>>>>>>>>>>>> for my app. I'm not sure if that's the cause of this bug, cos the code >>>>>>>>>>>>>>>> it's refering to hasn't changed in months, but I guess I best follow >>>>>>>>>>>>>>>> it all through and see what happens anyway. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 1:00 PM, jpff wrote: >>>>>>>>>>>>>>>>> If you build csound with 'set(CMAKE_BUILD_TYPE "Debug")' in you Custom.cmake >>>>>>>>>>>>>>>>> you would get more information. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, 5 May 2016, Peter Burgess wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Yes, that was from just before I changed the search path, this is a >>>>>>>>>>>>>>>>>> newer stack trace: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> #0 0x7ffff76f5b12 addaa() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #1 0x7ffff782e8fa kperf_nodebug() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #2 0x7ffff783004e csoundPerform() >>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>> #3 0x44f4b8 Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>> (/usr/local/include/csound/csound.hpp:276) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Which I will point out is different again. Is it usual for an error to >>>>>>>>>>>>>>>>>> appear to happen in 4 or more different places? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ps This might make you chuckle... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Leak_PossiblyLost\|====\|15,745,040 bytes in 1 blocks are possibly lost >>>>>>>>>>>>>>>>>> in loss record 5,511 of 5,512\| >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 15 MBs lost!!!! >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 12:46 PM, Steven Yi wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Are you sure about the header? It still says: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Thu, May 5, 2016 at 7:41 AM, Peter Burgess >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> recompiled against the correct header, but no dice. I'll watch some >>>>>>>>>>>>>>>>>>>> valgrind tutorials and get a grip on what all it's messages mean. Btw, >>>>>>>>>>>>>>>>>>>> I just got an error with a different stack trace again (this was still >>>>>>>>>>>>>>>>>>>> linked to the old header): >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> #0 0x7ffff76e68fe cs_hash_table_get() >>>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #1 0x7ffff76e54db csoundFindVariableWithName() >>>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #2 0x7ffff76ca8ce useropcdset() >>>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #3 0x7ffff76c6c93 insert() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #4 0x7ffff76d636f process_score_event() >>>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #5 0x7ffff76d6d2a sensevents() (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #6 0x7ffff782ffa8 csoundPerform() >>>>>>>>>>>>>>>>>>>> (/usr/local/lib/libcsound64.so.6.0:??) >>>>>>>>>>>>>>>>>>>> #7 0x44f48e Csound::Perform(this=0x6fae90 ) >>>>>>>>>>>>>>>>>>>> (csound/Csound6.05/include/csound.hpp:273) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>>> >>>>>>>>>>>>>> Csound mailing list >>>>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> http://algorythmradio.com >>>>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> http://algorythmradio.com >>>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://algorythmradio.com >>>>>>>>> https://soundcloud.com/algorythmradio >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> http://algorythmradio.com >>>>>>> https://soundcloud.com/algorythmradio >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> http://algorythmradio.com >>>>> https://soundcloud.com/algorythmradio >>>> >>>> >>>> >>>> -- >>>> http://algorythmradio.com >>>> https://soundcloud.com/algorythmradio >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> >> -- >> http://algorythmradio.com >> https://soundcloud.com/algorythmradio >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here