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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,57ca86d2263c2ca9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-31 14:12:18 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!colt.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Gnat: system__finalization_implementation__finalize_list Date: 31 Jan 2003 22:11:18 +0000 Organization: Pushface Sender: simon@smaug.pushface.org Message-ID: References: <3e379038$0$350$bed64819@news.gradwell.net> <3e38bbbc$0$346$bed64819@news.gradwell.net> NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1044051137 10274 62.49.19.209 (31 Jan 2003 22:12:17 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Fri, 31 Jan 2003 22:12:17 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Xref: archiver1.google.com comp.lang.ada:33660 Date: 2003-01-31T22:11:18+00:00 List-Id: "Alexander Boucke" writes: > I've had exactly the same problem using gnat-3.13p and the Booch > Components (bc-20000219). When using the managed memory pools from > the components the program would not close *after* executing all my > code correctly. In the debugger I've seen this error then... For me > the occurence of this error depends on the size of my lists and can > (seemingly) be avoided using unmanaged storage. And gnat-3.14p, > gnat-3.15p and gcc-3.2-gnat do not work at all for me due to > compiler errors :-( bc-20000219 is rather old. There was an error in that release of Managed_Storage (1.7), my log says revision 1.8 date: 2001/01/28 19:50:25; author: simon; state: Exp; lines: +3 -3 Deallocations were linked into the first available chunk, not the correctly-sized and -aligned one. which might have some bearing!