Date:         Thu, 13 Feb 2003 22:19:44 -0500
Reply-To:     Sigurd Hermansen <HERMANS1@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Sigurd Hermansen <HERMANS1@WESTAT.COM>
Subject:      Re: Segmentation Violation error
Comments: To: Ramesh Makkena <makkena@XOMA.COM>
Content-Type: text/plain; charset="iso-8859-1"

In my experience, a Segmentation Violation error, much like the MS Windows
Blue Screen of Death, means that a program is pointing to a memory location
outside memory allocated to that program. Often it means that a process
needs more memory than the system can provide.

Sig

-----Original Message-----
From: Ramesh Makkena [mailto:makkena@XOMA.COM]
Sent: Thursday, February 13, 2003 8:58 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Segmentation Violation error


Hello Folks,

SAS v8.2 , Solaris

I am getting the segmentation violation error when I run the proc report. I
get these errors frequently. I could n't find why?.

Has anybody got the following before :

Segmentation Violation In Task ( REPORT   ]
Fault Occurred at [/usr/local/sas/hotfix/sasexe/saspdpdf:pdf_mark+0xf84]

Task Traceback

/usr/local/sas/hotfix/sasexe/saspdpdf:pdf_mark+0xf84
/usr/local/sas/hotfix/sasexe/saspdpdf:yugtext+0xe4c
/usr/local/sas/sasexe/saspso:pdf_spcl+0x77c
/usr/local/sas/sasexe/saspso:place_+0x1934
/usr/local/sas/sasexe/saspso:psodoc+0x1c48
/usr/local/sas/sasexe/saspso:psodoc+0x3d38
/usr/local/sas/sasexe/saspso:place_+0x5118
/usr/local/sas/sasexe/saspso:place_+0x3a68
/usr/local/sas/hotfix/sasexe/sasrep7:reptmpl+0x7e8
/usr/local/sas/hotfix/sasexe/sasrep7:reptmpl+0xaf4
/usr/local/sas/sas.82ba62:odstrev+0x404
/usr/local/sas/sas.82ba62:sasoda+0x9cc
/usr/local/sas/sas.82ba62:odssm+0x278
/usr/local/sas/sas.82ba62:odsfact+0x2650
/usr/local/sas/hotfix/sasexe/sasrepmn:repmain+0x2cc8
/usr/local/sas/hotfix/sasexe/sasrepor:sasrepor+0x8c
/usr/local/sas/sas.82ba62:vvtentr+0x6c
NOTE: PROCEDURE REPORT used:
      real time           0.08 seconds
      cpu time            0.07 seconds

NOTE: The SAS System stopped processing this step because of errors.

Thanks,
Ramesh