topic Re: Cannot perform proc freq and chi sq test due to segmentation violation? in SAS Procedures

Cannot perform proc freq and chi sq test due to segmentation violation?

ALM8601 — Wed, 15 Jan 2020 17:04:47 GMT

Not sure what to do with this, contacted support and they told me to come here. Anyone that has encountered this, please advise. Thank you.

ERROR: An exception has been encountered.

Please contact technical support and provide them with the following traceback information:

The SAS task name is [FREQ (2)]

Segmentation Violation

Traceback of the Exception:

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/sas(+0x16a07e) [0x55cf6f18407e]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/sas(+0x4ecff) [0x55cf6f068cff]

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

Reeza — Wed, 15 Jan 2020 17:18:38 GMT

Restart SAS first, if you're using SAS UE, restart the VM, not Oracle Virtual Box, the actual VM.

If none of those work, I'd delete the VM (not Oracle) and re-add it. If you don't remove myfolders it will be fine. If you've customized your preferences/autoexec you'll need to reset that.

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

Rick_SAS — Thu, 16 Jan 2020 13:44:53 GMT

Please post your code and explain how you are running SAS (Univerisity Edition, Enterprise Guide, SAS Studio,....). Also include your version of SAS, which you can find by submitting

%put &SYSVLONG;

and copy/paste the result from the SAS log.

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

ALM8601 — Thu, 16 Jan 2020 16:14:33 GMT

No go...

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

Reeza — Thu, 16 Jan 2020 16:16:02 GMT

That's not super helpful, can you expand on exactly what you tried so far in detail.

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

ALM8601 — Thu, 16 Jan 2020 16:25:10 GMT

Using SAS University and SAS Studio.

Code:

*CHI-Square - general association;
PROC FREQ DATA = original;
TABLES Technique*Fu_visit_mo / chisq cmh;
RUN;

Version

1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

73 %put &SYSVLONG;

9.04.01M6P110718

74 run;

76 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

log

73 *CHI-Square - general association;

74 PROC FREQ DATA = original;

75 TABLES Technique*Fu_visit_mo / chisq cmh;

76 RUN;

ERROR: An exception has been encountered.

Please contact technical support and provide them with the following traceback information:

The SAS task name is [FREQ (2)]

Segmentation Violation

Traceback of the Exception:

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/sas(+0x16a07e) [0x558612c6707e]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/sas(+0x4ecff) [0x558612b4bcff]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7fb67754faa4]

/lib64/libpthread.so.0(+0xf7e0) [0x7fb678ac57e0]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0x9c3fe) [0x7fb614af13fe]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xa4c32) [0x7fb614af9c32]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(setGroupStructureValues+0xeb5) [0x7fb614af0445]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xb03a6) [0x7fb614b053a6]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(parsePdfElements+0x1118) [0x7fb614b03228]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(processAccessibilityValues+0x3b) [0x7fb614b020db]

/opt/sasinside/SASHome/SASFoundation/9.4/dbcs/sasexe/saspdpdf(yugextn+0x295) [0x7fb614a7fc95]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x51abc) [0x7fb614fa4abc]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7fb615012a47]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x4bde4) [0x7fb614f9ede4]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7fb615012a47]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x48c17) [0x7fb614f9bc17]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7fb615012a47]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(render_page+0x102d) [0x7fb614f7641d]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(place_+0x3aae) [0x7fb614f8555e]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x4572b) [0x7fb614f9872b]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x442d6) [0x7fb614f972d6]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(+0x429a7) [0x7fb614f959a7]

/opt/sasinside/SASHome/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7fb615012a47]

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

ERROR: An exception has been encountered.

Please contact technical support and provide them with the following traceback information:

The SAS task name is [FREQ (2)]

Segmentation Violation

NOTE: There were 40 observations read from the data set WORK.ORIGINAL.

NOTE: PROCEDURE FREQ used (Total process time):

real time 0.20 seconds

cpu time 0.16 seconds

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

Reeza — Thu, 16 Jan 2020 16:26:52 GMT

1. Did you restart your virtual machine?
2. Did you delete the vm and try re-adding it?
3. Has SAS UE crashed on you recently while working with big files?

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

ALM8601 — Thu, 16 Jan 2020 16:29:04 GMT

Yes, restarted VM didn't change anything.

Deleted the VM didn't change anything

SAS U has not crashed on me. My current file is very small

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

Reeza — Thu, 16 Jan 2020 16:32:24 GMT

You deleted the VM, downloaded a new image, added that and it didn't fix the issue?

What happens if you run the following:

proc freq data=sashelp.cars;
table make*origin;run;

If that runs, somethings wrong with your data. Otherwise, I'm out of suggestions.

Re: Cannot perform proc freq and chi sq test due to segmentation violation?

ALM8601 — Fri, 17 Jan 2020 15:12:52 GMT

That code worked, thank you.

Maybe I have something formatted wrong.