Home Original page

[Python-Dev] possible memory leak on windows (valgrind report)

Guido van Rossum guido at python.org
Mon Sep 19 19:05:00 CEST 2005 
So it is. I swear I saw "s"; I must've had an out of date version. The
change to "et" is less than a week old, but that's no excuse. :-(

It does look like the patch is correct then (but I can't build on
Windows any more either). Sorry for the confusion.

On 9/19/05, Neal Norwitz <nnorwitz at gmail.com> wrote:
> On 9/19/05, Guido van Rossum <guido at python.org> wrote:
> >
> > That patch doesn't make sense to me -- the "s" code to
> > PyArg_ParseTuple doesn't return newly allocated memory, it just
> > returns a pointer into a string object that is owned by the caller
> > (really by the call machinery I suppose). Compare other places using
> > PyArg_ParseTuple(args, "s:...").
> 
> "s"?  The format passed to ParseTuple is "et".  At least it is in the
> patch I'm looking at.
> 
> n
> 


-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev mailing list