Brian Pane <[EMAIL PROTECTED]> writes: > The worst thing that should happen in that scenario is a storage leak. > If you can isolate a test case that triggers the problem, please let > me know and I'll work on debugging it.
Thanks. The next step I'll take is to look for a thread safety issue with multiple threads doing an overlap using the same table for table b. If that doesn't explain the mangling and subsequent segfault, then I'll build a testcase with the same tables and see if I can make the overlap segfault. I changed the module to do an overlay operation and the storage leak and segfault are gone, but I hate not knowing what caused the segfault. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
