<br>umm i'm using pd-extended 0.41.4 . So in this case apart from gem which lib uses opengl ??<br><br>Sisil<br><br><div class="gmail_quote">On Sat, Aug 15, 2009 at 9:59 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 Fri, 7 Aug 2009, sisil mehta wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[ 6389.806394] pd[31100]: segfault at 4 ip b74d95dc sp bf987c90 error 6 in<br>
libstdc++.so.6.0.10[b7420000+e4000]<br>
[ 6545.228881] pd[31220]: segfault at 461 ip b70d22eb sp bfa37830 error 4 in<br>
gridflow.pd_linux[b7058000+30b000]<br>
</blockquote>
<br></div>
This is probably related to the ATI driver conflict we just talked about, unfortunately. The quick fix is to make sure Gem is not loaded (nor any other OpenGL thing), but when you actually need Gem to be loaded, it's a bit complicated.<br>
<br>
What the conflict does, is turn every error message of GridFlow into a crash. Therefore if you fix this, then you will see GridFlow's error messages correctly and will see what's wrong.<br>
<br>
(You can actually see those messages using gdb too, but it's a lot less cumbersome to remove the conflict first.)<br><font color="#888888">
<br>
_ _ __ ___ _____ ________ _____________ _____________________ ...<br>
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec</font></blockquote></div><br>