> I have valgrind reports indicating memory problems in score sorting. I
> will send these along if I can reproduce this problem this evening.

It is normal because `csoundCleanup' is not called with a segfault.
Here is the valgrind output with trapped.csd:

end of score.              overall amps:  31130.8  29985.6
           overall samples out of range:        0        0
0 errors in performance
Elapsed time at end of performance: real: 86.206s, CPU: 83.140s
512 1024 sample blks of shorts written to /home/audio/csound/sf/test.wav (WAV)
==19098== 
==19098== HEAP SUMMARY:
==19098==     in use at exit: 57,400 bytes in 212 blocks
==19098==   total heap usage: 25,555 allocs, 25,343 frees, 14,258,046 bytes allocated
==19098== 
==19098== LEAK SUMMARY:
==19098==    definitely lost: 0 bytes in 0 blocks
==19098==    indirectly lost: 0 bytes in 0 blocks
==19098==      possibly lost: 0 bytes in 0 blocks
==19098==    still reachable: 57,400 bytes in 212 blocks
==19098==         suppressed: 0 bytes in 0 blocks
==19098== Rerun with --leak-check=full to see details of leaked memory
==19098== 
==19098== For counts of detected and suppressed errors, rerun with: -v
==19098== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 275 from 5)

tito

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net