This is the mail archive of the
mailing list for the GCC project.
Re: 'stack overflow' message for Darwin; host hooks
- From: Dale Johannesen <dalej at apple dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: Dale Johannesen <dalej at apple dot com>, Geoffrey Keating <geoffk at apple dot com>, Zack Weinberg <zack at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 10 Feb 2003 12:28:43 -0800
- Subject: Re: 'stack overflow' message for Darwin; host hooks
On Thursday, February 6, 2003, at 02:03 PM, Mike Stump wrote:
This is not always true; at least 3 users ran into it before we added
the Apple local call
On Thursday, February 6, 2003, at 12:54 PM, Geoffrey Keating wrote:
I'm of two minds here. On the one hand, honoring the user's limits
It's too low for some highly atypical test cases, but in real
programs the limit is not a problem.
a good thing; on the other hand, we know that the default stack limit
is too low for us on Darwin and it seems to me that we ought not to
make the user worry about that.
to setrlimit that Mike refers to below.
Then you'll want to remove the Apple local code that bumps it up
automatically, then turn it loose on the community, and see if people
like the result. I think I know the answer. I think the answer is,
it is just way too low on darwin.
Yes, clearly this is a Darwin-specific problem. It seems to me having
the setrlimit call
on Darwin, but not elsewhere, is the right thing.