This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: help requested for diagnosing core dump

From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
To: Elkin David <djeklein at yahoo dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Wed, 20 Nov 2002 21:06:15 +0100
Subject: Re: help requested for diagnosing core dump
Organization: Moene Computational Physics, Maartensdijk, The Netherlands
References: <20021120161122.74219.qmail@web20204.mail.yahoo.com>

Elkin David wrote:

Could you help me track down the cause of a 'core
dump'
in a large Fortran 77 and C program?

After debugging manually, using 'dbg,' and adding
compiler flags I have not succeeded. Were it not for
the core dump, I would have thought all was fine since
all output is generated and has been checked for
accuracy.

Are you sure the core file is *new*, i.e., not a core file from a previous invocation of the program ?

What happens if you say: `gdb <executable> core' and issue the gdb command `where' ?

Hope this helps,

--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

References:
- help requested for diagnosing core dump
  - From: Elkin David

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