2011/11/11 Mathieu Bouchard matju@artengine.ca
Le 2011-11-11 à 19:50:00, tim vets a écrit :
ok, only difference here is that doing ctrl+c didn't kill pd (just
'^CQuit' in the gdb prompt.
That's what happens when pd (or whatever process being debugged) is already crashed.
#0 0xb7fe1424 in __kernel_vsyscall ()
#1 0xb7d55e71 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/** linux/raise.c:64 #2 0xb7d5934e in abort () at abort.c:92
That's a sign that it was trying to kill itself with signal 6 (ABORT).
#3 0xb7d8c577 in __libc_message (do_abort=2,
fmt=0xb7e658ac "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/**libc_fatal.c:189#4 0xb7d96961 in malloc_printerr (action=<value optimized out>, str=<value optimized out>, ptr=0x8612798) at malloc.c:6283
And it's because of a memory error that you ought to debug with Valgrind.
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.
hey, this is strange, when I run 'valgrind pdextended' and then create [fux_kinect] it doesn't hang, but just says:
[fux_kinect]: kinect initiated [fux_kinect]: Number of devices found: 0 [fux_kinect]: Could not open device
which sounds not so bad since I don't have a Kinect connected atm... 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...) running pdextended without valgrind, and then creating [fux_kinect] it still hangs pd and outputs b4551000-b45d2000 r-xp 00000000 08:11 16516148 /usr/lib/i386-linux-gnu/libfreetype.so.6.6.2Pd: signal 6 like before gr, Tim
______________________________**______________________________** __________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC