Hey,
I've only loaded the gridflow library in the beginninng....no other libs.

on the other thread by me discussing the crashing problem, i had updated the GF from svn as mathieu suggested, and it still crashed. i again ran the where and backtrace full commands and attached the new results in that thread.

Sisil.

On Sun, Aug 16, 2009 at 8:52 PM, Mathieu Bouchard <matju@artengine.ca> wrote:
On Sun, 16 Aug 2009, Michal Seta wrote:
I would suggest that for debugging purposes you start with pd-vanilla, so:
$sudo mv /usr/lib/pd/default.pdsettings /usr/lib/pd/default.pdsettings.bak
And if you created some custom settings you may have .pdsetting and/or
.pdrc in your $HOME
$mv ~/.pdsettings ~/pdsettings.bak
$mv ~/.pdrc ~/pdrc.bak

I should stress out that the leading "$" isn't part of the command!

I remember a beginners' intro to unix that prefixed every command with "%" in bold (the csh prompt). Some people actually retyped the "%" and got frustrated over it! But in that case, there was a space after the prompt character so it was more recognisable as such, than $mv. Frankly, I can imagine a script that has $sudo and $mv written in it for real and for a reason, which is the reason I decided to talk about this rather than not.


Following that, pd should start only with internals and no 3rd party objects.  Then you simply do pd -path /path/to/gf/ -lib gridflow and take it from there. And only then you start adding other libraries/externals until you find the conflicting setup.

Yeah, but if you don't want to do it blindly with trial and error, then you gotta use the «ldd» commands on all externals, and then «|grep libGL» on that.


 _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec