Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!carrow
From: carrow@nrl-cmf.UUCP (Steven Carrow)
Newsgroups: comp.sys.intel
Subject: General, probably stupid, questions about Intel architecture
Keywords: Intel, C, malloc, memory
Message-ID: <169@nrl-cmf.UUCP>
Date: 9 Feb 89 23:11:06 GMT
Organization: Society for the Creatively Deluded
Lines: 30


Greetings,

	I work at the Naval Research Laboratory and have no experience
with Intel boxes; I also have a friend in the same boat. However, she
is currently trying to program in C on a 320 (?) running a sort of quasi-,
pseudo-XENIX without adequate documentation (bear in mind that this is
all second-hand). Currently, she has an array of structures as a
global variable, with a size of about 3300 bytes. When she runs the
routine, it dies with a segmentation violation; if she merely declares
the pointer and mallocs the necessary space, the response is simply
"Killed". The machine is not large enough for man pages or a debugger
more sophisticated than adb, so all she can learn is that the stack
apparently overflows. My questions are as follows:

	a) What's the problem? Could she be running into an
architectural limit? I know very little about segmented architectures.

	b) Are good sources of info on writing C on the 320? Total clue-
lessness reigns here as well.

All responses appreciated.

*****************************************************************************
* Steven A Carrow               *      ARPA: carrow@itd.nrl.navy.mil        *
* Code 5570                     *      UUCP: uunet!nrl-css!carrow           *
* Naval Research Lab            *                                           *
* Washington, DC 20375          *      Disclaimer: I can barely speak for   *
* (202) 767-9125                *      myself, much less the government.    *
*****************************************************************************