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=ham 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!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.scarlet.biz!news.scarlet.biz.POSTED!not-for-mail NNTP-Posting-Date: Wed, 29 Nov 2006 11:23:01 -0600 From: Ludovic Brenta Newsgroups: comp.lang.ada Subject: Re: Possible heap problem on Windows, help sought References: <456d72b1$0$31519$39db0f71@news.song.fi> <456d9441$0$24608$39db0f71@news.song.fi> <4t5lq7F12jm1nU1@mid.individual.net> <456db855$0$24618$39db0f71@news.song.fi> Date: Wed, 29 Nov 2006 18:23:39 +0100 Message-ID: <873b82qi90.fsf@ludovic-brenta.org> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Cancel-Lock: sha1:9ctbwe4hApGNn0zd794A6feYC84= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 62.235.243.191 X-Trace: sv3-jV6wkgrE8i38KybaSvEnXiD4+S9PKR1EusWJX/mimSBFpBAWYUknJjhPWvJCidsPzAim8wLKq3t1zet!bP/WFM3a+w4hux0eC8w1t/SMfXqkBGunmiNw5j5sT6nchmbw0rD97cSYUGtyGSUuXvTD8yJZHk0= X-Complaints-To: abuse@scarlet.be X-DMCA-Complaints-To: abuse@scarlet.biz X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news2.google.com comp.lang.ada:7744 Date: 2006-11-29T18:23:39+01:00 List-Id: Niklas Holsti writes: > I'm grateful for your advice. Thanks to the Ada run-time checks it > has been a while since I had to fight with this kind of bug, but I > hope it will come back to me -- and then go away again :-) Same here; for the past coupld of months, I've been trying, on and off, to fight a nasty heap corruption bug in GPS 3.1.3, 4.0.0 and now 4.1.1. I've documented the various symptoms in Debian bugs #393636, #400876 and #400883. I realised that my skills are insufficient for such a large-scale undertaking; Valgrind detected more that 10 million errors during a short run of GPS, most of which in Python or GTK+ libraries, and not all of which are necessarily serious. Any advice? Today I replaced one instance of Unchecked_Deallocation with a no-op and behold, GPS no longer crashes. Obviously, it leaks, but that's not as bad as crashing or hanging. Because there was nothing obviously wrong with the Unchecked_Deallocation that I removed, I suspect there is still some heap corruption going on unnoticed. See my latest comment on #400876. I'm thinking maybe I should instrument access types to use debug pools, but there are too many of them. That's obviously not on Windows; sorry for hijacking your thread, Niklas :) -- Ludovic Brenta.