Hey,<br>I've only loaded the gridflow library in the beginninng....no other libs.<br><br>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.<br>
<br>Sisil.<br><br><div class="gmail_quote">On Sun, Aug 16, 2009 at 8:52 PM, Mathieu Bouchard <span dir="ltr"><<a href="mailto:matju@artengine.ca">matju@artengine.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Sun, 16 Aug 2009, Michal Seta wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would suggest that for debugging purposes you start with pd-vanilla, so:<br>
$sudo mv /usr/lib/pd/default.pdsettings /usr/lib/pd/default.pdsettings.bak<br>
And if you created some custom settings you may have .pdsetting and/or<br>
.pdrc in your $HOME<br>
$mv ~/.pdsettings ~/pdsettings.bak<br>
$mv ~/.pdrc ~/pdrc.bak<br>
</blockquote>
<br></div>
I should stress out that the leading "$" isn't part of the command!<br>
<br>
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.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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.<br>
</blockquote>
<br></div>
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.<div><div></div><div class="h5"><br>
<br>
_ _ __ ___ _____ ________ _____________ _____________________ ...<br>
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec</div></div></blockquote></div><br>