On Thu, 2013-02-14 at 07:21 +0100, Matthias Schwarzott wrote:
I will create a bug ticket to track this.
No time for the moment to look at your patch, but it is a good
idea to enter a bug in bugzilla with the patch and the before/after
diffs for the test.
Philippe
On 12.02.2013 10:12, Paul Menzel wrote:
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
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
Hi there!
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.
The attached patch
