Message 375313 - Python tracker

➜

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	T.Rex
Recipients	T.Rex, sanket, skrah
Date	2020-08-13.14:57:19
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1597330639.53.0.225037017034.issue41540@roundup.psfhosted.org>
In-reply-to

Content
Is it a 64bit AIX ? Yes, AIX is 64bit by default and only since ages, but it manages 32bit applications as well as 64bit applications. The experiments were done with 64bit Python executables on both AIX and Linux. The AIX machine has 16GB Memory and 16GB Paging Space. The Linux Fdora32/x86_64 machine has 16GB Memory and 8269820 Paging Space (swapon -s). Yes, I agree that the behavior of AIX malloc() under "ulimit -d unlimited" is... surprising. And the manual of malloc() does not talk about this. Anyway, does the test: if (size > (size_t)PY_SSIZE_T_MAX) was aimed to prevent calling malloc() with such a huge size? If yes, that does not work.

Is it a 64bit AIX ? Yes, AIX is 64bit by default and only since ages, but it manages 32bit applications as well as 64bit applications.

The experiments were done with 64bit Python executables on both AIX and Linux.

The AIX machine has 16GB Memory and 16GB Paging Space.

The Linux Fdora32/x86_64 machine has 16GB Memory and 8269820 Paging Space (swapon -s).

Yes, I agree that the behavior of AIX malloc() under "ulimit -d unlimited" is... surprising. And the manual of malloc() does not talk about this.

Anyway, does the test:   if (size > (size_t)PY_SSIZE_T_MAX)  was aimed to prevent calling malloc() with such a huge size? If yes, that does not work.

History
Date	User	Action	Args
2020-08-13 14:57:19	T.Rex	set	recipients: + T.Rex, skrah, sanket
2020-08-13 14:57:19	T.Rex	set	messageid: <1597330639.53.0.225037017034.issue41540@roundup.psfhosted.org>
2020-08-13 14:57:19	T.Rex	link	issue41540 messages
2020-08-13 14:57:19	T.Rex	create