This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Call for testers: libiberty/physmem.c

From: Mike Stump <mstump at apple dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Mike Stump <mrs at apple dot com>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Tue, 25 Feb 2003 14:58:14 -0800
Subject: Re: Call for testers: libiberty/physmem.c

On Monday, February 24, 2003, at 06:34 PM, Zack Weinberg wrote:

I have a theory.

My theory is that, on Darwin, RLIMIT_DATA is applied only to memory
allocation via brk(),

A multitude of bad behavior stops me from testing your theory. sbrk wraps and never fails. Touching memory dies way too soon, not sure why. [ trying harder ] Ok, no, it doesn't apply in that case either. It is ignored.

One way to confirm or falsify this theory would be to write a mini
program that allocates and dirties memory, using malloc, and see if
it maxes out at RLIMIT_DATA or RLIMIT_AS.

malloc swicthes over to mmap for larger things. When I use things that are small enough, neither stop it from allocating more than these limits.

References:
- Re: Call for testers: libiberty/physmem.c
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]