I have an additional thought on this bug. I am not quite sure how allocate works but it seems to me that both allocate and shared libraries use overlapping segments of memory. When I free or use what has been allocated using ALLOCATE I destroy what has been allocated by a shared library. I've seen segfaults in GSL when trying to free blocks, after I call ALLOCATE. I hope this can help chasing the bug.
----------- Sergey Plis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
