[chuck-users] chuck segfaults at startup on core2duo on linux jack
ssalazar at CS.Princeton.EDU
Wed Apr 18 14:48:15 EDT 2007
Yikes, sorry to hear that. Could you provide a stack trace of this?
That would be most helpful in figuring out the problem. Im not sure
if you're handy with gdb, but the easiest way to do it is like this:
$ gdb chuck
(gdb) run -v5 cw.ck
... (crash happens) ...
... (stack trace printed here) ...
Copying all of the output of that gdb session (including the chuck
log output) will be very helpful as that typically specifies exactly
where the crash is occurring.
It would also be helpful if you could provide the text of cw.ck, if
you don't mind. It can be assumed that cw.ck doesn't crash ChucK on
other machines, correct?
On Apr 18, 2007, at 1:49 AM, Ken Restivo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Alas, I am dead in the ChucK waters.
> Just got a new Core 2 Duo laptop. Built ChucK 188.8.131.52 for linux-
> jack. Planned to use this machine for ChucK experimentation and
> live performance.
> And then:
> $ chuck cw.ck
> Segmentation fault
> $ chuck --probe
> [chuck]: found 1 device(s) ...
> [chuck]: ------( chuck -- dac1 )---------------
> [chuck]: device name = "Jack Server"
> [chuck]: probe [success] ...
> [chuck]: # output channels = 2
> [chuck]: # input channels = 2
> [chuck]: # duplex Channels = 2
> [chuck]: default device = YES
> [chuck]: natively supported data formats:
> [chuck]: 32-bit float
> [chuck]: supported sample rates:
> [chuck]: 48000 Hz
> [chuck]: ------( chuck -- 3 MIDI inputs )------
> [chuck]:  : "Midi Through Port-0"Segmentation fault
> Sad. No ChucK for me! This is with the stock 184.108.40.206
> - -ken
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> -----END PGP SIGNATURE-----
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users