This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author segfaulthunter
Recipients segfaulthunter
Date 2008-05-31.18:32:46
SpamBayes Score 0.17417113
Marked as misclassified No
Message-id <1212258770.12.0.665769337301.issue3019@psf.upfronthosting.co.za>
In-reply-to
Content
I have tried building Python3a5 today using the tarball offered on your
internet site. 
The process './python -E setup.py build' keeps on allocating my memory
using more than 80% of my RAM, I am certain that it would have used more
if I had not cancelled it.
When I use ltrace to track the system calls and put it into the
Makefile, the resource usage still raises but much slower, if I use
ltrace and supply it a PID, the memory usage raises as fast as normal. I
think this is due to something in ltrace, it's understandable because it
produced a file of more than 600MB.

I attached an excerpt of the output of ltrace, showing you how the
system calls seem to repeat, and the output of './configure', 'make',
'uname -a', 'lspci' and 'lsmod' so you have some data about my system.
I also got a screenshot showing the output of htop, make and strace
together: http://img516.imageshack.us/img516/2275/screenshot1ab8.png.
Maybe the output of two different programs(ltrace and strace) will help
you too.
I tried out building the current SVN py3k branch, resulting in a similar
problem.
PS: It would help if you allowed uploading of multiple files to bug reports
History
Date User Action Args
2008-05-31 18:32:50segfaulthuntersetspambayes_score: 0.174171 -> 0.17417113
recipients: + segfaulthunter
2008-05-31 18:32:50segfaulthuntersetspambayes_score: 0.174171 -> 0.174171
messageid: <1212258770.12.0.665769337301.issue3019@psf.upfronthosting.co.za>
2008-05-31 18:32:49segfaulthunterlinkissue3019 messages
2008-05-31 18:32:47segfaulthuntercreate