|
From: Paul M. <pau...@us...> - 2013-02-12 09:12:50
|
Dear Matthias, I am new to Valgrind too. Reading the Mailing Lists and IRC Web page [1] there is also a developer list, where your patch might get more attention. Am Dienstag, den 12.02.2013, 07:13 +0100 schrieb Matthias Schwarzott: > Currently the valgrind-message for use-after-free for a memory pool > consists of the execution callstack and the callstack, where the > superblock was allocated. To better diagnose it I wanted to get also the > callstack of the place where MEMPOOL_FREE was called. Sounds like a nice idea to me. > The attached patch uses the new fields added for use-after-free messages > that show two callstacks. > It is just a proof of concept. > How could it be improved? Could you show a trace without and with your patch applied? Thanks, Paul [1] http://valgrind.org/support/ |