This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: safety of GCJ-generated code
- From: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Andrew Haley'" <aph at cambridge dot redhat dot com>, Adam Megacz <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
- Date: Thu, 20 Dec 2001 12:23:36 +1300
- Subject: Re: safety of GCJ-generated code
- References: <40700B4C02ABD5119F000090278766443BEE4F@hplex1.hpl.hp.com>
Boehm, Hans wrote:
>Yes. Though it doesn't sound to me like it's that hard if we just want to
>deal with the case in which the stack runs into a guard page, but you have
>plenty of swap space left. I think it gets much harder if you also want to
>consider the case in which you ran out of stack space because there's no
>more more memory or swap space to allocate the next stack page.
>
Are there platforms where this is likely to be a problem? Presumably to
avoid this sort of situation, Linux threads imposes a limit on stack
size (32MB, IIRC), which would usually be hit long before virtual memory
is exhausted. In the case where virtual memory really does run out the
kernel will just start killing apps.
regards
Bryce.