On Sun, Dec 5, 2010 at 5:10 AM, Michael Menegakis <arx...@gmail.com> wrote: > On Sun, Dec 5, 2010 at 4:57 AM, Michael Menegakis <arx...@gmail.com> wrote: >> On Sat, Dec 4, 2010 at 5:25 PM, Michael Menegakis <arx...@gmail.com> wrote: >>> On Sat, Dec 4, 2010 at 4:08 PM, Michael Menegakis <arx...@gmail.com> wrote: >>>> On Sat, Dec 4, 2010 at 3:58 PM, Michael Menegakis <arx...@gmail.com> wrote: >>>>> to lock rd_buffer >>>> >>>> More like the whole function from the inside now that I think about it >>> >>> Sorry for the spam. For future reference it seems that to make it >>> thread safe you'd need to go recursively through a few functions, such >>> as opening the q3log file which is triggered by printing on console. >>> >>> It's not impossible, but it's not just a line. >> >> Wrong again! Logic dictates only printing on its own could be locked >> and it'd be enough period. >> >> Sorry. > > Actually no.
I GOT IT! Last one I promise. Instead of using Com_Printf.. just use a single variable that only the main thread goes around and uses it for Printf! That way it's perfectly safe since one would have to mutex lock only the one variable. _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
