From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: gnatbind get stack overflow, how do I investigate the cause? Date: Thu, 30 Mar 2017 16:30:22 +0200 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:46507 Date: 2017-03-30T16:30:22+02:00 List-Id: On 30/03/2017 15:00, Petter Fryklund wrote: > after a couple of years with C# I'm back! I am currently porting a > large project from Ada-95 in ObjectAda to GNAT 17, first on Linux and > later on W7. I've managed to compile the all files, but gnatbind hits a > stack overflow. How do I get more information about the cause? Are you sure? Usually it is the compiler that runs out of memory. It happens very often if you have many generic instances. The only solution I know is splitting compilation units. Important is the "distance". If you move X into packet Q that is "with"-ed in the packet P where compiler ran out of memory that is the distance 1. This is not enough. The distance must be at least 2. Therefore separate bodies do not help. Packing generic instances into a collection package does not help. etc. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de