Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!cec2!news
From: abed@saturn.wustl.edu (Abed M. Hammoud)
Newsgroups: comp.lang.c
Subject: Re: Wierd core dump on sparc-1
Message-ID: <1991Jan24.214110.1478@cec1.wustl.edu>
Date: 24 Jan 91 21:41:10 GMT
References: <1991Jan23.232300.3698@lavaca.uh.edu> <1991Jan24.061653.22785@tkou02.enet.dec.com>
Organization: Washington University, St. Louis MO
Lines: 35

In article <1991Jan24.061653.22785@tkou02.enet.dec.com> diamond@jit345.enet@tkou02.enet.dec.com (Norman Diamond) writes:
>In article <1991Jan23.232300.3698@lavaca.uh.edu> jet@karazm.math.uh.edu ("J. Eric Townsend") writes:
>
>>I've got a rather simple little C program that dumps core at 
>>the first "{" of main() (according to gdb and saber).
>>Any hints as to what could be causing this?
>
>Probably incorrect initializations of automatic variables in main().
>Possibly an insufficient stack limit or other similar problem.
>
>>I'm about to run it
>>interpreted under saber-c, we'll see what that shows (and how long
>>it takes).
>
>Good idea.  Why didn't you try it before posting?
>--
>Norman Diamond       diamond@tkov50.enet.dec.com
>If this were the company's opinion, I wouldn't be allowed to post it.


	I had the same problem a couple of weeks ago. (also on a sparc
	1+ station). I was using a number of large arrays. by keeping
	the same array sizes and changing their type from double to 
	float the problem disappear. So for some reason it seems it has
	something to do with big arrays.

	I will be interested to know what really causes this problem.

	--------------------------------------------------------------
	| Abed  M. Hammoud			abed@saturn.wustl.edu|
	| Washington University.	        office:(314)726-7547 |
	| Electronic Systems & Signals Research Laboratory.          |
	| Dept. of Electrical/Biomedical Engineering.		     |
	| St.Louis Mo U.S.A                                          |
	--------------------------------------------------------------