Roy, Hmmm... See? The other responses are reduced to citing quotations from "Threads 101" which they don't realize that you don't need, or guessing at what you're trying to do.
I think you need to continue your "binary search debugging" (== "commenting out stuff)." You seem to be very lucky in this case, at least inferring from your statement that running a 2nd thread gets you to "kerpow" quite reliably. That's a blessing with threads... Just continue knocking out strategic (large, if possible) sections of your code (making sure that instantiations are matched--included or excluded-- with their associated releases--ie. if you comment out an object creation, make sure its destruction is commented out too), till you find what triggers the problem and what doesn't... BUT, sometimes you need to follow the problem areas INTO calls, as you narrow things down, to identify the true issues. Using FastMM4 with the advanced debugging options on, can often help too... If you already narrowed it down to TMimeMess, it may be time to single-step through those calls, or some other debugging techniques... Good luck. - - - - - - - - - - - How To Ask Questions The Smart Way Eric Steven Raymond http://catb.org/~esr/faqs/smart-questions.html ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
