On 2012-6-2 18:53, Diez B. Roggisch wrote:
Python does some special things that confuse valgrind. Don't bother.
http://svn.python.org/projects/python/trunk/Misc/README.valgrind
Thanks for the link.
It clears a lot of my confusing, such as uninitialized reading...
--
WQ
--
http://mail.python.
Qi writes:
> Hi guys,
>
> Is there any known memory leak problems, when embed Python 2.7.3
> in C++?
> I Googled but only found some old posts.
>
> I tried to only call Py_Initialize() and Py_Finalize(), nothing else
> between those functions, Valgrind still reports memory leaks
> on Ubuntu?
>
>
On 2012-5-29 23:29, Ulrich Eckhardt wrote:
Call the pair of functions twice, if the reported memory leak doesn't
increase, there is no problem. I personally wouldn't even call this a
leak then, but that depends a bit on the precise definition.
I should still call it a memory leak though it see
Am 29.05.2012 16:37, schrieb Qi:
> I tried to only call Py_Initialize() and Py_Finalize(), nothing else
> between those functions, Valgrind still reports memory leaks
> on Ubuntu?
Call the pair of functions twice, if the reported memory leak doesn't
increase, there is no problem. I personally woul
Hi guys,
Is there any known memory leak problems, when embed Python 2.7.3
in C++?
I Googled but only found some old posts.
I tried to only call Py_Initialize() and Py_Finalize(), nothing else
between those functions, Valgrind still reports memory leaks
on Ubuntu?
Is that a know problem? Did Pyt
