<br><br><div class="gmail_quote">2011/11/11 Mathieu Bouchard <span dir="ltr"><<a href="mailto:matju@artengine.ca" target="_blank">matju@artengine.ca</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 2011-11-11 à 19:50:00, tim vets a écrit :<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ok, only difference here is that doing ctrl+c didn't kill pd (just '^CQuit' in the gdb prompt.<br>
</blockquote>
<br></div>
That's what happens when pd (or whatever process being debugged) is already crashed.<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
#0 0xb7fe1424 in __kernel_vsyscall ()<br>
#1 0xb7d55e71 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/<u></u>linux/raise.c:64<br>
#2 0xb7d5934e in abort () at abort.c:92<br>
</blockquote>
<br></div>
That's a sign that it was trying to kill itself with signal 6 (ABORT).<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
#3 0xb7d8c577 in __libc_message (do_abort=2, <br>
fmt=0xb7e658ac "*** glibc detected *** %s: %s: 0x%s ***\n")<br>
at ../sysdeps/unix/sysv/linux/<u></u>libc_fatal.c:189<br>
#4 0xb7d96961 in malloc_printerr (action=<value optimized out>, <br>
str=<value optimized out>, ptr=0x8612798) at malloc.c:6283<br>
</blockquote>
<br></div>
And it's because of a memory error that you ought to debug with Valgrind.<br>
<br>
You told me that it crashed with such a memory error, and that's why I told you to make a report based on Valgrind in the first place. You didn't tell me about hanging (freezing). In the case of an actual freeze, you use GDB with Ctrl+c. If pd freezes while trying to abort... I don't know why that could happen, but fixing the abort will fix the freeze.<div>
<div></div><div><br>
<br></div></div></blockquote><div><br></div><div>hey, this is strange, when I run 'valgrind pdextended' and then create [fux_kinect] it doesn't hang, but just says:</div><div><br></div><div>[fux_kinect]: kinect initiated</div>
<div>[fux_kinect]: Number of devices found: 0</div><div>[fux_kinect]: Could not open device</div>
<div><br></div><div>which sounds not so bad since I don't have a Kinect connected atm...</div><div>I'll attach my pix_kinect.pd_linux here, in case anyone can try with a kinect connected (I'm +-150 km away from mine now...)</div>
<div>running pdextended without valgrind, and then creating [fux_kinect] it still hangs pd and outputs</div><div>b4551000-b45d2000 r-xp 00000000 08:11 16516148 /usr/lib/i386-linux-gnu/libfreetype.so.6.6.2Pd: signal 6</div>
<div>like before</div>
<div>gr,</div><div>Tim</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
______________________________<u></u>______________________________<u></u>__________<br>
| Mathieu BOUCHARD ----- téléphone : <a href="tel:%2B1.514.383.3801" value="+15143833801" target="_blank">+1.514.383.3801</a> ----- Montréal, QC</div></div></blockquote></div><br>