Re: Segmentation fault

["Eric G . Miller" <egm2@jps.net>]

On Tue, Feb 15, 2000 at 11:08:21PM +0900, Junichi Uekawa wrote:
> On Mon, 14 Feb 2000 11:43:25 -0800, "davidturetsky"
> <davidturetsky@email.msn.com> was crying out from somewhere about: Re:
> Segmentation fault


> davidturetsky> I believe this is the code 
>>	that was getting me into trouble, but it could be
> davidturetsky> elsewhere
> davidturetsky> 
> davidturetsky>     fscanf (file, "%s", Title);
> davidturetsky>     fscanf (file, "%d %d %d %d %d %d", 
>>	&m, &n, &it, &LT, &EQ, &GT);

> Probably, the input string was too long for the char* Title?  I don't
> know. MSC seems to let the stack be destroyed quite quietly.  It's a
> feature, methinks. Not too many segfaults when developing, but
> occasional BOD on using.

This is why, I think, that fgets is recommended over scanf/fscanf.
You'll always know the maximum of the data you read in. Of course, then
you still have to split it and check your input data matches what you
expected to receive.  Also, newlines and whitespace can pile up in
scanf/fscanf. It's generally recognized as being unsafe (like C/C++ in
general!).


-- 
+----------------------------------------------------+
| Eric G. Miller                        egm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc  |
+----------------------------------------------------+