Hey, running with gdb, the terminal showed: Waiting for connection request... ... connected OSS: requested audio buffer size 8820 limited to 8192 OSS: issuing first ADC 'read' ... ...done. [New Thread 0xb7e5c8d0 (LWP 9989)]
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7e5c8d0 (LWP 9989)] 0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766 766 const char *s = av[i].a_symbol->s_name; Current language: auto; currently c++ (gdb) Quit
Sisil..
On Sat, Aug 15, 2009 at 11:54 PM, sisil mehta sisilmet2000@gmail.comwrote:
Hey, @Mathieu :which linux flavour do u use?? Maybe if that os doesnt give these problems, i could switch over to it. Sisil.
On Sat, Aug 15, 2009 at 11:29 PM, Mathieu Bouchard matju@artengine.cawrote:
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera because
[#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ? this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty opinionated about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list