Has anyone got a variant of tpool.c which has the current interface
but creates a new thread per operation instead of using a pool?
(I'm trying to track down a memory corruption issue which disappears
with --disable-threads, and I'm hoping the load of complaints from
'valgrind-2.2.0 --tool=helgrind' is due to the thread pool rather
than genuine bugs or code which Helgrind can't deal with.)
Show replies by date