From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10253 invoked by alias); 10 Dec 2002 17:24:19 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 10234 invoked by uid 61); 10 Dec 2002 17:24:18 -0000 Date: Tue, 10 Dec 2002 09:24:00 -0000 Message-ID: <20021210172418.10233.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, thomas.tomter@ifi.uio.no From: ehrhardt@mathematik.uni-ulm.de Reply-To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, thomas.tomter@ifi.uio.no, gcc-gnats@gcc.gnu.org Subject: Re: other/7772: Errors while building openH323 X-SW-Source: 2002-12/txt/msg00559.txt.bz2 List-Id: Synopsis: Errors while building openH323 State-Changed-From-To: open->closed State-Changed-By: cae State-Changed-When: Tue Dec 10 09:24:17 2002 State-Changed-Why: This is not a gcc bug. Your kernel decides to kill a random process because it immediatly needs memory and there is none (e.g. for a packet arriving via the network). There's not much that gcc can do about this. Maybe you want to experiment with the overcommit settings in /proc (depends on your kernel version) or add more memory/swap space. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7772