From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Hunting Sigsev Errors
Date: 28 Mar 2001 08:34:52 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 14
Message-ID: <99s7nc$807$1@antares.lu.erisoft.se>
References: <3ac02f4b$0$14446$272ea4a1 AT news DOT execpc DOT com> <Um7w6.1128$eX4 DOT 241968 AT typhoon DOT tampabay DOT rr DOT com> <l48w6.369$083 DOT 262866 AT typhoon DOT tampabay DOT rr DOT com>
NNTP-Posting-Host: lws256.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Greg Donnells (gad AT donnesys DOT com) wrote:
: This code fragment will ALWAYS generate a SIGSEV before the LOG call. If it
: doesn't - I get real strange behavior out of the fread() function call.
: Changing the ARRAYSIZE to 512 fixes this - no more SIGSEV and no more wierd
: behavior out of fread(). Looks like some sort of allocation bug or internal
: limit is being reached (1024x516= ~.5M, but 512x516=~.25M).

Does a simple hello world program work? If so, perhaps FAQ 15.9 can
help?


Right,

						MartinS