|
From: Bart V. A. <bar...@gm...> - 2006-08-23 19:24:53
|
On 8/22/06, Josef Weidendorfer <Jos...@gm...> wrote: > > On Tuesday 22 August 2006 18:18, Bart Van Assche wrote: > > Hmmm... AFAIK, konqueror does not do multithreading. > Why does drd for the 1-threaded "segment" at process start already need > to store read/write accesses? I would say that there can never be any > race until a second thread is created. Josef, you're right about this. Not recording read and write accesses until a second thread is created would be a nice optimization of the drd tool. Or I am wrong and the drd tool is not storing read/write accesses for > konqueror, but only the 500627 (*) mallocs with stack traces for potential > later error messages. > I have tried to disable malloc()/free() wrapping, but I didn't see an obvious difference in memory consumption of the drd tool. |