On 2002.10.25, Andrew Piskorski <[EMAIL PROTECTED]> wrote: > Purify (with both gcc and Sun cc) reports various sorts of "errors", > none of which I can do anything about (in the vendor library), and I'm > not at all convinced they have anything to do with this problem > anyway.
Without being able to "play" with your system, just listening to the symptoms and examining the gdb stacktraces ... if I had to bet you a beer over what the problem was, I'd say your vendor library is not threadsafe and depending on if/how paranoid your mutex/locking is in your wrapper around their library, you may be letting it call some non-reentrant stuff and it's killing itself. That's how I'd bet, anyway. I'm probably wrong and this is definitely a WAG but it might lead you to look in the right direction ... > The only other experiments I've thought of are to try different > versions of AOLserver and/or Tcl. Basically, I'm mostly out of ideas > and insight, so if anyone has any, I'd appreciate hearing it. Thanks! Anything that calls into your third-party library, grab a shared mutex before and unlock it after. Basically, make sure that there is only ONE thread at any given point in time interacting with your third party library. Performance might suffer, but if that's what it takes to make your stuff work ... you can trade off correctness for performance, it's your choice. ;-) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
