Just want to report a strange crash I had, and what is obviously the  
problem. The message was:

orch compiler:
file too large for ortext space
csound(305) malloc: *** error for object 0x820800: incorrect checksum  
for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
Csound tidy up: Segmentation fault

But my orc wasn't extraordinary large. After a lot of testing I found  
that obviously the number of characters in a certain region of the orc  
led to the crash: one less or more is ok, but exactly this number  
crashes (can be spaces or whatever). Each time the report was  
referring to "object 0x820800"

I know this may sound crazy. It reminds me that I had a similar  
problem some time ago with a shell script calling csound, and a friend  
sent me a diagnosis made with valgrind. I attach this. Not sure  
whether this is helpful for anyone ...

	joachim

Do you have a CSD?

At 17:52 08/09/2009, you wrote:
>Just want to report a strange crash I had, and what is obviously the
>problem. The message was:
>
>orch compiler:
>file too large for ortext space
>csound(305) malloc: *** error for object 0x820800: incorrect checksum
>for freed object - object was probably modified after being freed.
>*** set a breakpoint in malloc_error_break to debug
>Csound tidy up: Segmentation fault
>
>But my orc wasn't extraordinary large. After a lot of testing I found
>that obviously the number of characters in a certain region of the orc
>led to the crash: one less or more is ok, but exactly this number
>crashes (can be spaces or whatever). Each time the report was
>referring to "object 0x820800"
>
>I know this may sound crazy. It reminds me that I had a similar
>problem some time ago with a shell script calling csound, and a friend
>sent me a diagnosis made with valgrind. I attach this. Not sure
>whether this is helpful for anyone ...
>
>         joachim
>
>
>
>
>
>
>
>------------------------------------------------------------------------------
>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>trial. Simplify your report design, integration and deployment - and focus on
>what you do best, core application coding. Discover what's new with
>Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes but it depends on some external files. I'll have a look  and then  
send it to you.
Thanks -
	joachim


Am 09.09.2009 um 11:50 schrieb Victor Lazzarini:

> Do you have a CSD?
>
> At 17:52 08/09/2009, you wrote:
>> Just want to report a strange crash I had, and what is obviously the
>> problem. The message was:
>>
>> orch compiler:
>> file too large for ortext space
>> csound(305) malloc: *** error for object 0x820800: incorrect checksum
>> for freed object - object was probably modified after being freed.
>> *** set a breakpoint in malloc_error_break to debug
>> Csound tidy up: Segmentation fault
>>
>> But my orc wasn't extraordinary large. After a lot of testing I found
>> that obviously the number of characters in a certain region of the  
>> orc
>> led to the crash: one less or more is ok, but exactly this number
>> crashes (can be spaces or whatever). Each time the report was
>> referring to "object 0x820800"
>>
>> I know this may sound crazy. It reminds me that I had a similar
>> problem some time ago with a shell script calling csound, and a  
>> friend
>> sent me a diagnosis made with valgrind. I attach this. Not sure
>> whether this is helpful for anyone ...
>>
>>        joachim
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports  
>> 2008 30-Day
>> trial. Simplify your report design, integration and deployment -  
>> and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The error message "file too large for ortext space" means that despite
the calculations and extension the orchestra characters have
overflowed the allocation.  Basically this should not happen so I
really would like to see what triggered it.
==John ffitch

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net