Hi,

today, I wanted to test the behavior of my csound application by feeding it
with a faulty score file (and a valid orchestra). Here it is: 

f1 0 32769 10 1

i1 0 10 8000
f ; wrong statement

My application segfaulted. After a while of debugging, I found out that the
fault occured in csoundCompile(). Out of curiosity, I ran the same score
with the csound executable (5.07), with the same result (occurring during
"sorting score ..."). The segfault is easily reproducible:  it seems that a
single (invalid) "f" statement in a score crashes csound. This is probably
not a big issue as it is rather rare that a user makes such a mistake, but I
still wanted to report it. I hope this list is the right place to do that.

Alex
-- 
View this message in context: http://www.nabble.com/segfault-in-csoundCompile%28%29-tp15365009p15365009.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks, Alex, for this bug report.  Anything that causes Csound to crash is
a problem :)

I am pretty familiar with the score parser, so I will look into this -- if
not for 5.08, then for 5.09.

Thanks.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Alex Weiss wrote on 2/8/08 5:14 PM:

> 
> Hi,
> 
> today, I wanted to test the behavior of my csound application by feeding it
> with a faulty score file (and a valid orchestra). Here it is:
> 
> f1 0 32769 10 1
> 
> i1 0 10 8000
> f ; wrong statement
> 
> My application segfaulted. After a while of debugging, I found out that the
> fault occured in csoundCompile(). Out of curiosity, I ran the same score
> with the csound executable (5.07), with the same result (occurring during
> "sorting score ..."). The segfault is easily reproducible:  it seems that a
> single (invalid) "f" statement in a score crashes csound. This is probably
> not a big issue as it is rather rare that a user makes such a mistake, but I
> still wanted to report it. I hope this list is the right place to do that.
> 
> Alex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net