Hi<br>
Thanks for the answers!<br>
<br>
Yes, the problem was sintax.<br>
Missing return statments was a mistake, but not the mistake. Calling a
function creating a new float variable was the mistake which originated
the nullpointexc.<br>
Now I understand and I'm happy :-)<br>
<br>
Very grateful<br>
Lucas<br>
<br>
<br><br><div><span class="gmail_quote">2008/4/19, eduard aylon <<a href="mailto:eduard.aylon@gmail.com">eduard.aylon@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Lucas,<br> <br> I think the problem comes from PercAditiva::setResonancia(dur dt,<br> float factor) where you call env[i].setDecay( dt, float factor ). Note<br> that you are calling the function and creating a new float factor. I<br>
guess it should be env[i].setDecay( dt, factor ). Doing so, no<br> exceptions/errors/segfaults occur in my system.<br> <br><br> eduard<br> <br><br> <br> On 19 Apr 2008, at 03:05, lucas samaruga wrote:<br> > Hi Kas<br>
><br> > Yes, I speak Spanish, and with great difficult, English. The Spanish<br> > comments are not important.<br> > And yes, the seg-fault menssage is a linux menssage, not a ChucK<br> > menssage (if I understood what you say).<br>
><br> > Thanks you<br> > Lucas<br> ><br> ><br> > 2008/4/18, Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>>: On 19/04/2008,<br> > lucas samaruga <<a href="mailto:samarugalucas@gmail.com">samarugalucas@gmail.com</a>> wrote:<br>
> Hi list<br> ><br> > Hi Lucas!<br> ><br> ><br> > I'm working with ChucK in a musical project,<br> ><br> > Yay! A wise choice too, much better then ChucK for database<br> > management, probably. :¬)<br>
><br> ><br> > and I have a problem with the code.<br> > This code generates 3 different error menssages in my machine<br> > (running chuck-alsa on linux), depending on the amount of<br> > components in an array.<br>
><br> > I just glanced over it but I suspect at least issue 2) is one of the<br> > (new?) issues where (un)certain problems of resolving type on arrays<br> > (maybe especially when using functions) leads to seg-faults.<br>
><br> > There's good news in that Ge is looking into this and I found so far<br> > that in all cases where I ran into this (if it's the same thing) so<br> > far we can write around it.<br> ><br> > Another thing worth mentioning is that ChucK shouldn't seg-fault at<br>
> all. Maybe it should kill the shred when the error happens or give a<br> > error at compilation but not seg-fault and quite working altogether.<br> ><br> > It's rather late here and your comments are in a language I don't<br>
> speak (I think Spanish?) so I hope you'll excuse me if I don't have<br> > a solution right away but that issue is likely to be fixed<br> > relatively soon and I rate suspect we could work around it as well.<br>
> Just not right now :¬)<br> ><br> ><br> ><br> ><br> > Yours,<br> > Kas.<br> ><br> > _______________________________________________<br> > chuck-users mailing list<br> > <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br> ><br> ><br> > _______________________________________________<br> > chuck-users mailing list<br>
> <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br> > <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br> _______________________________________________<br> chuck-users mailing list<br> <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
</blockquote></div><br>