This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debugging options

From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
To: "Salvatore Filippone" <salvatore dot filippone at uniroma2 dot it>
Cc: fortran at gcc dot gnu dot org
Date: Mon, 30 Oct 2006 12:33:23 +0100
Subject: Re: Debugging options
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gQURjmp4GOxeCtaImCZ9ZD0klCChf44KK8EWAhFEbCPockS5cvRu7bgkyqU+qfU63LyoMk+WpBVWgLZtoQoPY0tIbpyEoG/w1dfhBZznkxrbYv/CzaO6oERywAlTMMCphKC42pgPzGTiB8cse0zJCF8AcWC3XsEfJTa6ckBlQpc=
References: <1162206305.3723.12.camel@localhost>

Is there a way to force gfortran compiled code to produce a core dump or
a  backtrace upon hitting a runtime library error? (Short of starting
the program under the debugger, which is a bit cumbersome if the program
is MPI based and only some of the processes display the error)


I don't think there's a way to do that currently, but it shouldn't be
too hard to add. Could you file an enhancement bug about this?

FX

Follow-Ups:
- Re: Debugging options
  - From: Salvatore Filippone

References:
- Debugging options
  - From: Salvatore Filippone

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]