|
From: Julian S. <js...@ac...> - 2006-08-27 17:52:24
|
> These wrappers certainly can be re-enabled. One reason why I disabled them > is that the algorithm in drd for reporting allocation call stacks is not > fool-proof: e.g. when free() is called after a race occurred but before it > is reported, then no call stack will be printed. True; but given that we need all the info we can to make sense of race addresses, and also considering the overhead isn't that large, I don't care if the algorithm isn't foolproof. If it turns out to be a problem we can easily enough add a freed blocks queue, like memcheck has, so then it will be able to print a backtrace for addresses in recently freed blocks. J |