On Dec 2, 2007, at 9:52 AM, Christiaan Hofman wrote: > That may have been a side effect of the bug we had a while ago where > the connection was accessed from the wrong thread. I'm quite sure > our connections don't need to be multi treaded. In fact, when that > exception occurs it's probably a sign of a bug in our code which we > should fix rather than ignore by allowing multiple threads to access > the connection.
Well, for someone who hates being wrong, I'm sure wrong a lot...your suggestion was spot on. I went back and checked the backtrace for that exception report and discovered that it occurred in - [BDSKSharingServer serverDidSetup], which was calling stopDOServer from the server thread. I added an assert in stopDOServer to catch this case; since stopDOServer uses the ivar directly, the assertion in the accessor was never hit. thanks! adam ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
