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=-2.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,d139a44b4dd6bc63 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!news1.google.com!news.maxwell.syr.edu!newsfeed.vmunix.org!news.cs.univ-paris8.fr!proxad.net!cleanfeed1-a.proxad.net!nnrp19-1.free.fr!not-for-mail Return-Path: X-Greylist: delayed 8711 seconds by postgrey-1.24 at green; Wed, 29 Nov 2006 15:20:24 CET From: Duncan Sands To: comp.lang.ada@ada-france.org Subject: Re: Possible heap problem on Windows, help sought Date: Wed, 29 Nov 2006 15:20:00 +0100 User-Agent: KMail/1.9.5 References: <456d72b1$0$31519$39db0f71@news.song.fi> <456d9441$0$24608$39db0f71@news.song.fi> In-Reply-To: <456d9441$0$24608$39db0f71@news.song.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 at math.u-psud.fr X-Virus-Scanned: amavisd-new at ada-france.org Cc: Niklas Holsti X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.9rc1 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.ada Message-ID: X-Leafnode-NNTP-Posting-Host: 88.191.17.134 Organization: Guest of ProXad - France NNTP-Posting-Date: 29 Nov 2006 15:25:01 MET NNTP-Posting-Host: 88.191.14.223 X-Trace: 1164810301 news-4.free.fr 13655 88.191.14.223:49440 X-Complaints-To: abuse@proxad.net Xref: g2news2.google.com comp.lang.ada:7739 Date: 2006-11-29T15:25:01+01:00 > Well I made a small test program using my ordinary compilation options > (-g -O2 -gnato -fstack-check) and it happily allocated and used 300 MB > of heap, as I asked it to, so it seems that this is not a heap problem. > Sorry for a mistaken hypothesis, I should have checked it before posting > my question. But the problem remains and any advice will be gratefully > received, although I now suspect that the cause may be a programming > error, a Heisenbug that disappears in the debugger and does not manifest > on Linux for some reason. It could well be memory corruption or the use of an uninitialized variable. These both have a tendency to manifest themselves differently in the debugger. Try running your program under valgrind. Ciao, Duncan.