From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11086 invoked by alias); 6 May 2003 08:26:54 -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 10853 invoked by uid 71); 6 May 2003 08:26:40 -0000 Date: Tue, 06 May 2003 08:26:00 -0000 Message-ID: <20030506082640.10852.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Christian Ehrhardt" Subject: Re: other/10628: core file not generated Reply-To: "Christian Ehrhardt" X-SW-Source: 2003-05/txt/msg00355.txt.bz2 List-Id: The following reply was made to PR other/10628; it has been noted by GNATS. From: "Christian Ehrhardt" To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, khan_sanjay@operamail.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/10628: core file not generated Date: Tue, 6 May 2003 10:17:07 +0200 On Mon, May 05, 2003 at 02:34:51PM -0000, bangerth@dealii.org wrote: > Creation of core files is not controlled by the compiler, but > by the shell. Use for example ulimit. The shell may play a role, but the application can catch SIGSEGV and exit instead of dumping core. IIRC this is what gcc does and IMHO it is a valid feature request that gcc should have an option to actually make the backends dump core. regards Christian -- THAT'S ALL FOLKS!