From: "Scott Johnson" <[EMAIL PROTECTED]> > Here's one debug technique we've used for reproducing "lock leaks" much more > efficiently: deliberate over-locking. Instead of locking suspect memory > objects just once (with a single MemHandleLock call and corresponding > MemHandleUnlock), lock with multiple MemHandleLock's (say 14) and unlock > correspondingly. Then instead of needing 15 passes through the offending > code path, it should take only one or two. Or if it's valid for certain > types of objects to have nested locks, just reduce that overlock constant as > needed. > Now *that's* a good idea. Whoever's responsible for the 'debugging' section of the PalmOS Companion should be taking notes about now.
Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
