Hi! On 01/28/2014 06:26 PM, [email protected] wrote: > Hi! > > That is one of the posible solutions. > > I would create the thread safe library on the top of the one we have now > and created set of calls with _r suffix (as libc does with strerror(), > ctime(), ...). Then we can use these when needed and link the the test > against both -lltp and -lltp_mt (or whatever it gets called). That would > include all the tst_res() functions and maybe some other, we can add > these once they. > > The open question is the callback() because we either need to redirect > all calls that gets the callback pointer as an parameter or create the > callback indirection (with pthread once) in the test. I would rather see > the second variant. What we can do is a macro that will decleare the > pthread once etc given the name of the real callback and the name of the > resulting function. > OK, that would work. I'm sending first two patches to separate common code from tst_res.c and to declare callback() in multi-threaded tests.
Thanks, Alexey ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
