|
From: Julian S. <js...@ac...> - 2006-08-23 19:30:31
|
On Wednesday 23 August 2006 20:24, Bart Van Assche wrote: > 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. That is indeed try (and the DIOTA paper mentions exactly this optimisation); however I would prefer first to simplify the memory management scenario as much as possible until we can figure out what's going on, and fix it. > I have tried to disable malloc()/free() wrapping, but I didn't see an > obvious difference in memory consumption of the drd tool. No, maybe not, but let's leave it disabled for now since that gives a simpler situation to debug. J |