[PD] pix_openni crash Pd

[Jack]

Le 24/02/2012 17:18, Mathieu Bouchard a écrit :
> Le 2012-02-24 à 16:03:00, Jack a écrit :
>
>> But when i create the Gemwin, Pd crash :
>> Erreur de segmentation
>> I did something bad ?
>
> des plantages comme ça sont injustifiables.
>
> ressaye avec gdb et/ou valgrind.
>
>  ______________________________________________________________________
> | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC

Hello Mathieu,

Here the output with valgrind when i create the gemwin :

==4048== Invalid read of size 4
==4048==    at 0x49C6B94: GemBase::gem_MessCallback(void*, _symbol*, 
int, _atom*) (GemBase.cpp:237)
==4048==    by 0x80B5809: pd_typedmess (in /usr/bin/pd)
==4048==  Address 0x735ef68 is 0 bytes after a block of size 32 alloc'd
==4048==    at 0x4025315: calloc (vg_replace_malloc.c:467)
==4048==    by 0x80B8710: getbytes (in /usr/bin/pd)
==4048==
==4048== Invalid read of size 1
==4048==    at 0x49C6814: GemBase::gem_startstopMess(int) (GemBase.cpp:102)
==4048==    by 0x49C6B9E: GemBase::gem_MessCallback(void*, _symbol*, 
int, _atom*) (GemBase.cpp:237)
==4048==    by 0x80B5809: pd_typedmess (in /usr/bin/pd)
==4048==  Address 0x11 is not stack'd, malloc'd or (recently) free'd
==4048==
==4048==
==4048== Process terminating with default action of signal 11 (SIGSEGV)
==4048==  Access not within mapped region at address 0x11
==4048==    at 0x49C6814: GemBase::gem_startstopMess(int) (GemBase.cpp:102)
==4048==    by 0x49C6B9E: GemBase::gem_MessCallback(void*, _symbol*, 
int, _atom*) (GemBase.cpp:237)
==4048==    by 0x80B5809: pd_typedmess (in /usr/bin/pd)
==4048==  If you believe this happened as a result of a stack
==4048==  overflow in your program's main thread (unlikely but
==4048==  possible), you can try to increase the size of the
==4048==  main thread stack using the --main-stacksize= flag.
==4048==  The main thread stack size used in this run was -1.
==4048==
==4048== HEAP SUMMARY:
==4048==     in use at exit: 65,622,038 bytes in 45,892 blocks
==4048==   total heap usage: 114,083 allocs, 68,191 frees, 143,231,167 
bytes allocated
==4048==
==4048== LEAK SUMMARY:
==4048==    definitely lost: 17,149 bytes in 61 blocks
==4048==    indirectly lost: 10,576 bytes in 607 blocks
==4048==      possibly lost: 320,500 bytes in 4,906 blocks
==4048==    still reachable: 65,273,813 bytes in 40,318 blocks
==4048==         suppressed: 0 bytes in 0 blocks
==4048== Rerun with --leak-check=full to see details of leaked memory
==4048==
==4048== For counts of detected and suppressed errors, rerun with: -v
==4048== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 2643 from 11)
socket receive error: Connection reset by peer (104)
Erreur de segmentation

Thanx.
++

Jack