https://bugs.kde.org/show_bug.cgi?id=460142
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
(In reply to Simon Richter from comment #0)
> The three stack traces I get (allocation, deallocation and use) show what is
> happening, but it is difficult for me to find the point where the string is
> given to Python -- the function to intern the string is called quite often,
> so I can't just easily break there.
Waiting for valgrind to provide some support to record auxiliary stack traces
as you suggest,
what you might do is to capture this stack trace and print it together with the
ptr for the memory allocated
and given to python.
Then when valgrind reports a 'use after free' error, you can search in the
program output the last
stack trace that mention this pointer.
--
You are receiving this mail because:
You are watching all bug changes.
