LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (October 2003, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Tue, 7 Oct 2003 10:41:38 -0700
Reply-To:   m n <iced_phoenix@YAHOO.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   m n <iced_phoenix@YAHOO.COM>
Organization:   http://groups.google.com
Subject:   Re: Segmentation Violation In Task ( UNIVARIA ]
Content-Type:   text/plain; charset=ISO-8859-1

HERMANS1@WESTAT.COM (Sigurd Hermansen) wrote in message news:<9B501B3774931C469BCCCC021BE537228EE7F7@remailnt2-re01.westat.com>... > 'Segmentation Violation In Task ( UNIVARIA ]' generally means that the > process (UNIVARIATE) cannot allocate enough memory to complete the > summaries.

Interesting...could you elaborate on something though? From my C programming days, I understood segmentation faults to generally mean that a program was attempting to access a memory location that it didn't own (as determined by the OS). Applying this knowledge to this SAS error, it sounds like SAS, behind the scenes, may be attempting to use memory it doesn't own to fulfill a request that requires more memory than SAS is given by the OS. Why wouldn't SAS recognize that it was out of memory and print a related message, rather than blindly attempt to carry out the user's request and seg fault?

Thanks, Matt


Back to: Top of message | Previous page | Main SAS-L page