matju at artengine.ca
Sat Nov 12 18:34:13 CET 2011
Le 2011-11-12 à 18:19:00, tim vets a écrit :
> 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.
> indeed, when creating [fux_kinect], valgrind says:
> ==3908== Invalid write of size 4
> ==3908== at 0x417017E: pthread_cond_init@@GLIBC_2.3.2 (pthread_cond_init.c:43)
So, when will you apply the fix I gave in a previous mail ?
> ==3908== Address 0x4389460 is not stack'd, malloc'd or (recently) free'd
Did you just remove the malloc line entirely ? Put the correct line I gave
To get rid of malloc/free, you need make more changes than just that
(removing * in some places and adding & in some other places).
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
More information about the Pd-list