[chuck-users] A problem with the code

lucas samaruga samarugalucas at gmail.com
Thu Apr 24 20:38:00 EDT 2008


Hi
Thanks for the answers!

Yes, the problem was sintax.
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.
Now I understand and I'm happy :-)

Very grateful
Lucas



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


More information about the chuck-users mailing list