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.

Title: Python3a5 compile failing due to high memory usage
Type: compile error Stage:
Components: Build Versions: Python 3.0
Status: closed Resolution: duplicate
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, segfaulthunter
Priority: normal Keywords:

Created on 2008-05-31 18:32 by segfaulthunter, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
output segfaulthunter, 2008-05-31 18:32 Output of various commands.
gdb_output segfaulthunter, 2008-05-31 19:34 Output of GDB
Messages (3)
msg67585 - (view) Author: Florian Mayer (segfaulthunter) Date: 2008-05-31 18:32
I have tried building Python3a5 today using the tarball offered on your
internet site. 
The process './python -E 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
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
PS: It would help if you allowed uploading of multiple files to bug reports
msg67587 - (view) Author: Florian Mayer (segfaulthunter) Date: 2008-05-31 19:34
Added the output of GDB as the memory usage was nearing 70%.
Hope it helps.
msg67589 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2008-05-31 21:29
Turns out this is due to GCC 4.3 being used. Dupe of #2626.
Date User Action Args
2022-04-11 14:56:35adminsetgithub: 47269
2008-05-31 21:29:18georg.brandlsetstatus: open -> closed
resolution: duplicate
messages: + msg67589
nosy: + georg.brandl
2008-05-31 19:34:45segfaulthuntersetfiles: + gdb_output
messages: + msg67587
2008-05-31 18:32:49segfaulthuntercreate