Date:	Fri, 29 Apr 1994 23:08:05 -0400
From:	morphine AT whatever DOT cs DOT jhu DOT edu (Michael Phelps)
Sender:	morphine AT whatever DOT cs DOT jhu DOT edu
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Segmentation violation

	I've been compiling several programs over the past day to test out gcc,
and sometimes I can get a program to compile fine, but when I run it, I get a
message like
	"Segmentation violation in pointer 0x00000010 at d8:5c9d
	(register values)
	Call frame traceback EIPs:
		0x00005c9d
		0x00001e7a
		0x00001702
		0x0000121d
	"

First of all, what exactly does this mean?  Second, what can I do to keep it
from happening.  It doesn't matter whether I use the coff2exe program or run it
with go32, some programs simply show this error without hardly even starting.
There are only two things I have been able to come up with that are consistent
with all programs that crash this way: 1) they use pointers, and 2) they access
files.  I haven't tried isolating them further (ie, to find out if it is just
with files, or happens with all kinds of pointers).  Suggestions?  (It compiles
correctly on two other compilers.)
							---Michael Phelps
							   morphine AT cs DOT jhu DOT edu

- Raw text -