[PD] fux_kinect
Mathieu Bouchard
matju at artengine.ca
Sat Nov 12 18:16:17 CET 2011
Le 2011-11-11 à 21:54:00, tim vets a écrit :
> 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
The valgrind log (in the terminal) also ought to tell you an «Invalid
Write» error with a partial backtrace. This is the error message I told
you to give to the author, and even though it might not crash, it's still
usually a sign of major problems.
Whenever you have a crash while doing malloc/new, hunt down the Invalid
Writes that you see and it will usually fix the problem.
If it doesn't fix the problem, then it's because there
are other Invalid Writes that valgrind couldn't detect.
______________________________________________________________________
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
More information about the Pd-list
mailing list