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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,fb264cdd67c2f20f X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!m79g2000cwm.googlegroups.com!not-for-mail From: "Steve Whalen" Newsgroups: comp.lang.ada Subject: Re: Possibly fixed in gcc 4.1.1, but bug box -- Was: Re: A smaller self contained test case ... Date: 2 Jul 2006 18:38:19 -0700 Organization: http://groups.google.com Message-ID: <1151890699.675297.250220@m79g2000cwm.googlegroups.com> References: <05lkrrojfd.fsf@hod.lan.m-e-leypold.de> <16veqny46o.fsf_-_@hod.lan.m-e-leypold.de> <4gdbbqF1ld2nsU1@individual.net> NNTP-Posting-Host: 68.238.140.115 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1151890703 19692 127.0.0.1 (3 Jul 2006 01:38:23 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 3 Jul 2006 01:38:23 +0000 (UTC) User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: m79g2000cwm.googlegroups.com; posting-host=68.238.140.115; posting-account=GBMmzA0AAABrZ0dHOASa3b2Cdf-RliH9 Xref: g2news2.google.com comp.lang.ada:5422 Date: 2006-07-02T18:38:19-07:00 List-Id: M E Leypold wrote: > ... > Oh d***. I compile a lot of real live code. So I'm not even sure > wether my program isn't illegal somwhere but got accepted by > unjustifiedly by 3.15p. > ... I share your dilemma about Ada compilers, so here's a late post with perhaps an insight into your original bug report. I too still use GNAT 3.15p and ran your original cut down bug test on 3.15p on both Windows and Linux Debian Sarge. I got slightly different results, which may indicate your segfault was really a memory allocation problem in the 2nd half of the program. The bug test program on Linux blew up with: "raised PROGRAM_ERROR : stack overflow (or erroneous memory access)" which is interesting because my Windows version of your test program ran "successfully" to completion. It just ran (quickly through the "write" phase, then took forever (5+ minutes) on the "read" phase on a slow (450mhz) computer and used up memory like crazy. It was using over 30 megabytes of memory before it finished (I think it started at less then 1 megabyte). The output files were identical from all runs. So maybe 3.15p does NOT actually blow up, so much as abuse memory in some way that evidences different outcomes depending on the environment. Dmitry's idiom may help, but I thought I'd report this, since it looks to me like there may only be one problem, and that's a memory problem in the "read" phase that just causes different symptoms. Steve