On Tue, 22 Nov 2005, Fredrik Lundh wrote:
[...]
http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Misc/README.valgrind?view=markup
The up-to-date version of that (from SVN instead of old CVS repository) is
here:
http://svn.python.org/view/python/trunk/Misc/README.valgrind?view=markup
Hello,
Purify is not so difficult to use: just run and learn to read the output ;-)
My config: Win2k using VC6sp5, and only 512Mb RAM.
I downloaded the snapshot dated 2005/11/21 05:01,
commented out #define WITH_PYMALLOC,
built in debug mode,
modified the rt.bat file to use purify,
and ran rt -d.
Neal Norwitz:
I think a bigger bang for the buck would be to buy a Windows box with
Purify. Rational was a real pain to deal with, maybe it's better now
that IBM bought them. Parasoft (Insure++) was even worse to deal
with.
My experience with the other Windows option, BoundsChecker, is
Neal Norwitz wrote:
I think a bigger bang for the buck would be to buy a Windows box with
Purify. Rational was a real pain to deal with, maybe it's better now
that IBM bought them. Parasoft (Insure++) was even worse to deal
with. There would be many other benefits for someone to do more
On 11/21/05, Fredrik Lundh [EMAIL PROTECTED] wrote:
I don't think there's a shortage of Windows boxes among the python-dev
crowd (I have plenty). Does anyone knows that kind of box you need to
run purify these days ?
Dunno, but it would probably be fine on a reasonably new box with at
least
Neal Norwitz wrote:
There are still 2 memory leaks while running the regression tests.
They show up when running test_fork1 and test_pty. There may be more,
valgrind crashed on me the last run which was also before I fixed some
of the reference leaks. It would be great if people could
On 11/20/05, Martin v. Löwis [EMAIL PROTECTED] wrote:
Can somebody please give a quick explanation how valgrind can give
*any* reasonable leak analysis when obmalloc is used? In the current
implementation, obmalloc never ever calls free(3), so all pool memory
should appear to have leaked.
I would really like it if someone could run Purify (or another memory
tool) on Windows. Purify on any another (unix) platform would be
nice, but I doubt it will show much more. By using different tools,
problems not found by one tool may be found by the other. Plus there
is windows specific
Neal Norwitz wrote:
[...]
To give you an example, I ran the entire regression suite through
Valgrind after configuring --without-pymalloc. I only found 3
additional problems in new code. There was also one problem in older
code (Python/modsupport.c).
The big benefit of running with
Neal Norwitz wrote:
I still think the total references at the end of a test run are high,
342291. I don't have anything to base this number on. Some strategic
interning should help this number go down a bit. I suppose I
shouldn't worry much since these references don't seem to become
There's still more clean up work to go, but the current AST is
hopefully much closer to the behaviour before it was checked in.
There are still a few small memory leaks.
After running the test suite, the total references were around 380k
(down from over 1,000k). I'm not sure exactly what the
11 matches
Mail list logo
