From:	ville DOT sjoberg AT swipnet DOT se (Ville Sjoberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: file max sizes?
Date:	Wed, 12 Mar 1997 06:17:47 GMT
Organization:	-
Lines:	26
Message-ID:	<5g4i4c$5f0@mn5.swip.net>
References:	<01bc2ca1$660fce80$31c9c2d0 AT bonk>
NNTP-Posting-Host:	dialup94-5-3.swipnet.se
NNTP-Posting-User:	s-222948
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

"Jeffrey A Studer" <jstuder AT flash DOT net> wrote:

>Hello all,
> it seems that
>reading 40 bytes from a file at once, occasionally gives a SIGSEGV fault at
>runtime ( I wish i knew what these runtime error messages meant, as well. 
>Is there a FAQ on DOS error messages? ). 

SIGSEGV is not even a DOS error message, as far as I know, but an Unix
one. It supposedly stands for "signal: segment violation". That is --
your program has tried to write to a memory segment without write
permission. (if you didn't know, the memory in protect mode is split
up in segments, and the different programs can have read, write or
execute permission for a given segment) When you are programming in a
highlevel laguage like C, the compiler usually takes care such
low-level obstacles. In my experience, a sigsegv usually means that
you have tried to write through an uninitialized pointer: You should
check that possibility out. If you cannot find the error you should
consider using a debugger to find out where things went wrong. Good
luck!
----------------------------------------------
Vilhelm "Ville" Sjoeberg
Sci-fi geek, paranoid cyberpunk, celloplayer
PGP key available at www.villeweb.home.ml.org
"The future is not what it used to be."

- Raw text -