Have you guys tried valgrind? That can often pinpoint memory corruoption right at the source. It can be slow, but prefiltering the trace for SSL might help (if that's what's triggering it). Robin -- Robin Sommer * Phone +1 (510) 722-6541 * robin at icir.org ICSI/LBNL * Fax +1 (510) 666-2956 * www.icir.org