[CSOUND-DEV] problems with current dev branch...

[CSOUND-DEV] problems with current dev branch...

Date	2015-10-08 14:35
From	Rory Walsh
Subject	[CSOUND-DEV] problems with current dev branch...
	The current dev branch has broken Cabbage on me. As soon as I try to delete a Csound object, and recreate it, I get: 0 0x00007ffff5bfbcc9 __GI_raise /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c 56 1 0x00007ffff5bff0d8 __GI_abort /build/buildd/eglibc-2.19/stdlib/abort.c 89 2 0x00007ffff5c38394 __libc_message /build/buildd/eglibc-2.19/libio/../sysdeps/posix/libc_fatal.c 175 3 0x00007ffff5c4466e malloc_printerr /build/buildd/eglibc-2.19/malloc/malloc.c 4996 4 0x00007ffff5c4466e _int_free /build/buildd/eglibc-2.19/malloc/malloc.c 3840 5 0x00007ffff68075f6 memRESET 6 0x00007ffff6961e96 reset 7 0x00007ffff695db40 csoundDestroy 8 0x0000000000502ae7 Csound::~Csound /usr/local/include/csound/csound.hpp 863 9 0x0000000000502b16 Csound::~Csound /usr/local/include/csound/csound.hpp 869 This means I can only load one instrument in Cabbage. After that I need to close Cabbage, restart, and open another instrument. Any ideas what might have caused this?

Date	2015-10-08 14:40
From	Rory Walsh
Subject	Re: [CSOUND-DEV] problems with current dev branch...
	This looks like it is related to a problem I reported some months back, because now I keep get an invalid kr message too. Time for me to search the archives... On 8 October 2015 at 16:35, Rory Walsh <rorywalsh@ear.ie> wrote: The current dev branch has broken Cabbage on me. As soon as I try to delete a Csound object, and recreate it, I get: 0 0x00007ffff5bfbcc9 __GI_raise /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c 56 1 0x00007ffff5bff0d8 __GI_abort /build/buildd/eglibc-2.19/stdlib/abort.c 89 2 0x00007ffff5c38394 __libc_message /build/buildd/eglibc-2.19/libio/../sysdeps/posix/libc_fatal.c 175 3 0x00007ffff5c4466e malloc_printerr /build/buildd/eglibc-2.19/malloc/malloc.c 4996 4 0x00007ffff5c4466e _int_free /build/buildd/eglibc-2.19/malloc/malloc.c 3840 5 0x00007ffff68075f6 memRESET 6 0x00007ffff6961e96 reset 7 0x00007ffff695db40 csoundDestroy 8 0x0000000000502ae7 Csound::~Csound /usr/local/include/csound/csound.hpp 863 9 0x0000000000502b16 Csound::~Csound /usr/local/include/csound/csound.hpp 869 This means I can only load one instrument in Cabbage. After that I need to close Cabbage, restart, and open another instrument. Any ideas what might have caused this?

Date	2015-10-08 14:44
From	Rory Walsh
Subject	Re: [CSOUND-DEV] problems with current dev branch...
	A clean and rebuild on all my Csound projects, along with Csound seems to have sorted the issue. For the 100th time, please accept my sincerest apologies for the noise! On 8 October 2015 at 16:40, Rory Walsh <rorywalsh@ear.ie> wrote: This looks like it is related to a problem I reported some months back, because now I keep get an invalid kr message too. Time for me to search the archives... On 8 October 2015 at 16:35, Rory Walsh <rorywalsh@ear.ie> wrote: The current dev branch has broken Cabbage on me. As soon as I try to delete a Csound object, and recreate it, I get: 0 0x00007ffff5bfbcc9 __GI_raise /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c 56 1 0x00007ffff5bff0d8 __GI_abort /build/buildd/eglibc-2.19/stdlib/abort.c 89 2 0x00007ffff5c38394 __libc_message /build/buildd/eglibc-2.19/libio/../sysdeps/posix/libc_fatal.c 175 3 0x00007ffff5c4466e malloc_printerr /build/buildd/eglibc-2.19/malloc/malloc.c 4996 4 0x00007ffff5c4466e _int_free /build/buildd/eglibc-2.19/malloc/malloc.c 3840 5 0x00007ffff68075f6 memRESET 6 0x00007ffff6961e96 reset 7 0x00007ffff695db40 csoundDestroy 8 0x0000000000502ae7 Csound::~Csound /usr/local/include/csound/csound.hpp 863 9 0x0000000000502b16 Csound::~Csound /usr/local/include/csound/csound.hpp 869 This means I can only load one instrument in Cabbage. After that I need to close Cabbage, restart, and open another instrument. Any ideas what might have caused this?

Date	2015-10-08 14:50
From	Felipe Sateler
Subject	Re: [CSOUND-DEV] problems with current dev branch...
	Does cabbage work when compiled against an old version and run against the new? If not, then that should be a bug, as the ABI is supposed to be forward-stable until the major version is bumped. On 8 October 2015 at 10:44, Rory Walsh wrote: > A clean and rebuild on all my Csound projects, along with Csound seems to > have sorted the issue. For the 100th time, please accept my sincerest > apologies for the noise! > > On 8 October 2015 at 16:40, Rory Walsh wrote: >> >> This looks like it is related to a problem I reported some months back, >> because now I keep get an invalid kr message too. Time for me to search the >> archives... >> >> On 8 October 2015 at 16:35, Rory Walsh wrote: >>> >>> The current dev branch has broken Cabbage on me. As soon as I try to >>> delete a Csound object, and recreate it, I get: >>> >>> 0 0x00007ffff5bfbcc9 __GI_raise >>> /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c 56 >>> 1 0x00007ffff5bff0d8 __GI_abort >>> /build/buildd/eglibc-2.19/stdlib/abort.c 89 >>> 2 0x00007ffff5c38394 __libc_message >>> /build/buildd/eglibc-2.19/libio/../sysdeps/posix/libc_fatal.c 175 >>> 3 0x00007ffff5c4466e malloc_printerr >>> /build/buildd/eglibc-2.19/malloc/malloc.c 4996 >>> 4 0x00007ffff5c4466e _int_free >>> /build/buildd/eglibc-2.19/malloc/malloc.c 3840 >>> 5 0x00007ffff68075f6 memRESET >>> 6 0x00007ffff6961e96 reset >>> 7 0x00007ffff695db40 csoundDestroy >>> 8 0x0000000000502ae7 Csound::~Csound >>> /usr/local/include/csound/csound.hpp 863 >>> 9 0x0000000000502b16 Csound::~Csound >>> /usr/local/include/csound/csound.hpp 869 >>> >>> This means I can only load one instrument in Cabbage. After that I need >>> to close Cabbage, restart, and open another instrument. Any ideas what might >>> have caused this? >> >> > -- Saludos,

Date	2015-10-08 15:12
From	Rory Walsh
Subject	Re: [CSOUND-DEV] problems with current dev branch...
	It should, otherwise it is a problem. But I'm not sure why this happens, but each time I update my Csound build I get problems. I looked back through my notes from the last time this happened and "memo to self" reads delete csound repo re-clone rebuild That seems to have done the trick again. Something gets mangled when I try to update. Anyhow, as I said, it's all good now. On 8 October 2015 at 16:50, Felipe Sateler <fsateler@gmail.com> wrote: Does cabbage work when compiled against an old version and run against the new? If not, then that should be a bug, as the ABI is supposed to be forward-stable until the major version is bumped. On 8 October 2015 at 10:44, Rory Walsh <rorywalsh@ear.ie> wrote: > A clean and rebuild on all my Csound projects, along with Csound seems to > have sorted the issue. For the 100th time, please accept my sincerest > apologies for the noise! > > On 8 October 2015 at 16:40, Rory Walsh <rorywalsh@ear.ie> wrote: >> >> This looks like it is related to a problem I reported some months back, >> because now I keep get an invalid kr message too. Time for me to search the >> archives... >> >> On 8 October 2015 at 16:35, Rory Walsh <rorywalsh@ear.ie> wrote: >>> >>> The current dev branch has broken Cabbage on me. As soon as I try to >>> delete a Csound object, and recreate it, I get: >>> >>> 0 0x00007ffff5bfbcc9 __GI_raise >>> /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c 56 >>> 1 0x00007ffff5bff0d8 __GI_abort >>> /build/buildd/eglibc-2.19/stdlib/abort.c 89 >>> 2 0x00007ffff5c38394 __libc_message >>> /build/buildd/eglibc-2.19/libio/../sysdeps/posix/libc_fatal.c 175 >>> 3 0x00007ffff5c4466e malloc_printerr >>> /build/buildd/eglibc-2.19/malloc/malloc.c 4996 >>> 4 0x00007ffff5c4466e _int_free >>> /build/buildd/eglibc-2.19/malloc/malloc.c 3840 >>> 5 0x00007ffff68075f6 memRESET >>> 6 0x00007ffff6961e96 reset >>> 7 0x00007ffff695db40 csoundDestroy >>> 8 0x0000000000502ae7 Csound::~Csound >>> /usr/local/include/csound/csound.hpp 863 >>> 9 0x0000000000502b16 Csound::~Csound >>> /usr/local/include/csound/csound.hpp 869 >>> >>> This means I can only load one instrument in Cabbage. After that I need >>> to close Cabbage, restart, and open another instrument. Any ideas what might >>> have caused this? >> >> > -- Saludos, Felipe Sateler

Date	2015-10-08 18:30
From	Phil Sobolik
Subject	[CSOUND-DEV] Is digest broken
	I used to get csound-dev in digest format - a day's messages in one email. Is this broken because of the new branch? I'm getting

Date	2015-10-08 19:18
From	jpff
Subject	Re: [CSOUND-DEV] Is digest broken
	Humm.. You are registered to receive digest; I just checked Subscription Type Regular [NODIGEST] * Digest (traditional) [NOMIME DIGEST] Digest (MIME format) [NOHTML MIME DIGEST] Digest (HTML format) [HTML DIGEST] Index (traditional) [NOHTML INDEX] Index (HTML format) [HTML INDEX] On Thu, 8 Oct 2015, Phil Sobolik wrote: > I used to get csound-dev in digest format - a day's messages in one email. > Is this broken because of the new branch? I'm getting individual emails for > each message.