A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-November/018354.html below:

[Python-Dev] Memory leaks and uninitialized memory

[Python-Dev] Memory leaks and uninitialized memory [Python-Dev] Memory leaks and uninitialized memoryFredrik Lundh fredrik@pythonware.com
Sun, 4 Nov 2001 17:13:58 +0100
hi neal,


> I just submitted a bunch of patches to SF to correct memory leaks, 
> possible memory leaks, and uninitialized memory reads (UMR).  

(I tried to follow up over at sourceforge, but all I get is an error
message saying "ERROR!" and nothing else...)

I'm a bit puzzled over your proposed SRE patch.

the patch changes

        return PyString_FromString("");

to

        result = PyString_FromString("");
        Py_INCREF(result);
        return result;

but both according the documentation and the implementation,
FromString returns a new reference (usually another reference
to the internal nullstring object).

in other words, if there's a bug somewhere, I'm not sure it's in
SRE.

> What is the best format to post this info?  Would there be a better
> way to deal with these kinds or problems?

keep on posting them to this list, until someone comes up
with a better idea.

</F>




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4