From owner-freebsd-questions@FreeBSD.ORG  Wed Mar 21 15:15:13 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8BC201065670
	for <freebsd-questions@freebsd.org>;
	Wed, 21 Mar 2012 15:15:13 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.103.93])
	by mx1.freebsd.org (Postfix) with ESMTP id 0EFEE8FC21
	for <freebsd-questions@freebsd.org>;
	Wed, 21 Mar 2012 15:15:06 +0000 (UTC)
Received: from dc.cis.okstate.edu (localhost [127.0.0.1])
	by dc.cis.okstate.edu (8.14.5/8.14.5) with ESMTP id q2LEoPqM078354
	for <freebsd-questions@freebsd.org>;
	Wed, 21 Mar 2012 09:50:25 -0500 (CDT)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <201203211450.q2LEoPqM078354@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <78352.1332341425.1@dc.cis.okstate.edu>
Date: Wed, 21 Mar 2012 09:50:25 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Freebsd9.0 and the fgets directive in gcc
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 15:15:13 -0000

I've got some code which I wrote about 6 or 8 years ago that
apparently doesn't get along right now with FreeBSD9.0. In the
problem code, there is a loop that uses fgets to read a line
from a file. It runs properly until the 2708TH iteration and
then it dumps core with a segmentation fault.

char string0[256];
more lines of code . . .

while ( fgets(string0,sizeof(string0),fp_config)) {
code to be run for each line
}

	It runs fine until the 2,709TH iteration. Instead of
reading the next line, it jumps to the line that closes
fp_config even though it is far from read and exits with the
segmentation fault.

	The man page on fgets says that if errors occur while
running fgets, one must use perr to see whether the error
terminated activity or it was the end of the file. In this case,
it is definitely the error.

	Some observations:

The crash occurs on the 2,709TH input no matter how long I
declared string0 to be. string0 is over-written each new
iteration so nothing should be accumulating that uses up
resources.

	Maybe I am declaring string0 in the wrong data type.
Originally, it had been 1024 characters long but 2709 seems to
be the C equivalent to the apocalypse and I thought it was
supposed to be next December:-)

	This same code, by the way, also fails at about the same
number of iterations if one uses fgetc and  builds the line one
char at a time.