Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Robert Klemme <shortcutter@googlemail.com>
Newsgroups: comp.lang.java.programmer
Subject: Re: [opinion] javac's default stack space
Date: Mon, 10 Mar 2014 18:33:14 +0100
Lines: 18
Message-ID: <bo6barFk52iU1@mid.individual.net>
References: <slrnlhoufj.rhr.avl@login.logic.tuwien.ac.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net K8qLJh95EaC+9+ro5scYFwCxQymP+N8MZqKoW44tfJ0rng4oU=
Cancel-Lock: sha1:dnFgqlwRktNT7K8oZ5XcSmWDB9E=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
In-Reply-To: <slrnlhoufj.rhr.avl@login.logic.tuwien.ac.at>
Xref: csiph.com comp.lang.java.programmer:27714

On 09.03.2014 15:25, Andreas Leitgeb wrote:

> Has anyone else run into javac's default stack size limit?

Never.

> Does anyone else have any insight about what features of
> Java sources are likely culprits for stack usage peaks?

Can't you identify that from the source where it bails out?  Otherwise 
anything which requires recursion to process.  That might happen during 
parsing of deeply nested structures.  That is just a guess though.

Kind regards

	robert