Date: Wed, 17 Sep 2008 18:55:49 +0200 From: Pietro Cerutti <gahr@FreeBSD.org> To: Andrew MacIntyre <andymac@bullseye.apana.org.au> Cc: freebsd-hackers@freebsd.org Subject: Re: unexpected behaviour of malloc() on 7.0/amd64 Message-ID: <48D13695.2070000@FreeBSD.org> In-Reply-To: <48D12AD4.1000806@bullseye.andymac.org> References: <48D12AD4.1000806@bullseye.andymac.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Andrew MacIntyre wrote: [snip] | In investigating a Python 2.6rc1 regression test failure on FreeBSD | 7.0/amd64, as far as I can tell, malloc() does not return NULL when | available memory (including swap) is exhausted - the process just gets | KILLed. [snip] | The Python regression test concerned does not fail on FreeBSD 7.0/i386, | however the C program below exhibits the unexpected behaviour on both | 7.0/amd64 and 7.0/i386. The C program below does behave as | expected on FreeBSD 6.3/i386; I cannot currently test its behaviour on | FreeBSD 6.3/amd64. [snip] | Is this the intended behaviour? I can confirm something strange happening on i386/7.0-RELEASE: | ./malloc Killed | While on i386/8.0-CURRENT the behavior is as expected: | ./malloc_test chunks allocated: 2936 | [snip] | | Thanks, | Andrew. | - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjRNpQACgkQwMJqmJVx946uhQCfcWVVNnIXOIZ5PrmnenEjgLcT gQYAoNpwNxsW94EnOpMHQoit+OOgNd02 =mGSL -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48D13695.2070000>