[chuck-users] [BUG] otf blocks at error

Spencer Salazar spencer at ccrma.stanford.edu
Tue Feb 14 13:34:17 EST 2012

Hey Kassen,

Thanks for the bug report. We have been making some internal
improvements to the OTF system, so nows a good time to also clean up
bugs like these. Can you let me know if this is the current release
version you are using, or the latest SVN build, which I believe at one
point you were dabbling with.


On Thu, Feb 2, 2012 at 12:52 PM, Kassen <signal.automatique at gmail.com> wrote:
> Some more data points;
> It turns out I was mistaken and that a [enter] doesn't get the command
> to "unblock" and a Ctrl+c is needed. I also got this;
> $ chuck -v + otf_b.ck
> [chuck]:(2:SYSTEM): setting log level to: 5 (INFORM)...
> [chuck]:(5:INFORM): examining otf command '+'...
> [chuck]:(5:INFORM): otf connect:
> [chuck]:(5:INFORM):  | sending file:args 'otf_b.ck' for add...
> [otf_b.ck]:line(23).char(9): syntax error
> [chuck]: skipping file 'otf_b.ck' for [add]...
> Which seems to indicate that it gets past the error reporting before
> it gets stuck, which counts against my previous speculation that error
> reporting might be causing issues. Oh, well, that's what speculation
> is for.
> Yours,
> Kas.
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

More information about the chuck-users mailing list