In message <[EMAIL PROTECTED]>, Frank
Millman <[EMAIL PROTECTED]> writes
>> You could then also categorize this by type, e.g.
If you want a nice GUI and no requirement to modify your code Python
Memory Validator could be useful. http://www.softwareverify.com
Stephen
--
Stephen Kellett
Object M
Martin v. Löwis wrote:
> Frank Millman wrote:
> > In principle I agree. My concern was that I might have inadvertently
> > done something wrong (e.g. left a reference dangling) which would
> > prevent gc from removing all objects which I wanted to be removed.
>
> Depends on what it really is that
Frank Millman wrote:
> In principle I agree. My concern was that I might have inadvertently
> done something wrong (e.g. left a reference dangling) which would
> prevent gc from removing all objects which I wanted to be removed.
Depends on what it really is that you want to know. If you want
to kn
Paul Rubin wrote:
> "Frank Millman" <[EMAIL PROTECTED]> writes:
> > Is this a sensible approach, or are there easier ways to achieve this?
>
> In general you're supposed to just let gc do its thing. Doing your
> own storage management defeats the purpose of gc.
In principle I agree. My concern w
"Frank Millman" <[EMAIL PROTECTED]> writes:
> Is this a sensible approach, or are there easier ways to achieve this?
In general you're supposed to just let gc do its thing. Doing your
own storage management defeats the purpose of gc. At most I'd say
check for leaks by running some native extensi
Hi all
I don't know whether this will be of interest, but I have just carried
out an exercise that I found useful, so I thought I would share it.
I am writing a multi-user business app, with a multi-threaded server
program to handle client connections. The server should 'serve
forever'. Each clie
