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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ab4f67f984ef04f9 X-Google-Attributes: gid103376,public Path: controlnews3.google.com!news1.google.com!news.glorb.com!prodigy.com!atl-c02.usenetserver.com!news.usenetserver.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Tue, 25 May 2004 15:43:36 -0500 Date: Tue, 25 May 2004 16:43:36 -0400 From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Is the Ada run-time required to detect out-of-memory References: <878yfmiuak.fsf@insalien.org> <2h7b84Fa2aefU1@uni-berlin.de> <87n041l9mv.fsf@insalien.org> In-Reply-To: <87n041l9mv.fsf@insalien.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: NNTP-Posting-Host: 24.147.90.114 X-Trace: sv3-bWv9pn6Pzvxx3//hI3QNxq+wAPNLsJHiVrWuVjdgCbv8HMMuWKddp2U8IrOUiTEeTq5cyhmpKK7Sqdi!Rv0RbctL7yMS6M9MJqbk+Otivtd0jewBdhBRuORrGTk+htHOSd3N60uBcXEKMA== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net 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.1 Xref: controlnews3.google.com comp.lang.ada:824 Date: 2004-05-25T16:43:36-04:00 List-Id: Ludovic Brenta wrote: > I just closed your bug report after determining that the issue was not > in libgnat but in the kernel. Basically, Linux sends SIGKILL to > programs that exhaust physical RAM; as you know, SIGKILL cannot be > caught so libgnat has no chance to raise an exception. If the virtual > memory is exhausted before physical memory is, then libgnat does raise > Storage_Error. Did you refile the bug against the kernel? As I understand it now, the problem is not that the kernel raises SIGKILL if physical RAM is exhausted, but that malloc doesn't check that the allocation can succeed before making it. Having said that, I suspect that this should be a low priority bug, and it will be pretty hard to fix. It may take adding a version of malloc that does the check, and leaving the decision as to which one to call to the compiler run-time. (GNAT should then use the new call when allocating storage pools, and probably continue using the current version for allocations in the default storage pool. -- Robert I. Eachus "The terrorists rejoice in the killing of the innocent, and have promised similar violence against Americans, against all free peoples, and against any Muslims who reject their ideology of murder. Their barbarism cannot be appeased, and their hatred cannot be satisfied. There's only one way to deal with terror: We must confront the enemy and stay on the offensive until these killers are defeated." -- George W. Bush