One other thing to think about is something I do often which is to have a "suspend needed" boolean variable for threads. So if a suspend is needed it will be processed at an appropriate section of code where the thread itself knows whether or not it is indeed safe. Other wise it will remain pending for that thread until such time as it can reach a suspended state, trip another flag, and suspend.
So these issues are not trivial but are somewhat easy to ensure safety during suspend/resume calls. Just requires a bit of advanced skills when dealing with threads to remove risks associated with causing race conditions. On Wed, Sep 22, 2010 at 9:27 AM, José Mejuto <[email protected]> wrote: > Direct use of suspend/resume in i386 at least is a call for serious > and very, very difficult to track problems. A simple code like: -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
