Click here to Skip to main content
15,881,027 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I'm not a Unix guy so I really need some help on this. We have an NC machine post processor that runs on an old HP Unix box. Over the past few years, we have been migrating away from this machine so we haven't used this post for several years. We now have a need to to use this post processor again but we found that it no longer works because it fails with the following error:

Pid 4408 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
Memory fault(coredump)

We did some research and found that this the last time we used this post processor was back in 2009. We took the last file that posted successfully and ran it through the post again but it also fails with the same error. The executable has not changed since 2002 so we know that is not the issue. Also, per our IT department, the hardware has not been touched since then. They also supposedly moved the executable to a a similar Unix box and they are getting the same error on that box. If we are running the same file using the same executable on the same hardware, why would it stop working all of the sudden? To make things worse, we no longer have the source for this post processor due to a company buyout. Our IT department said they checked the disk space on the box and that their is plenty of room. Without the source, it would take several months to recreate this post to run on a different system. I'm still thinking it has to be the hardware. As a test, we created a real small file to post and we were able to get it to work which again leads me to believe its a hardware memory issue. Does anyone have any ideas on what we should try next? Any help with this would be greatly appreciated.
Posted
Comments
Florian Trück 8-Feb-14 8:32am    
Did your IT department check if the swap partition is sufficient enough?
Normally the process would use the RAM of the machine and when there is not enough space it will swap to disk on the /swap partition. If this partition is not big enough the process will crash. Possibly with the SIGSEGV.
Also a failure in RAM can be the cause. Maybe you should run a memtest and see if everything is ok. Also have a look if the hard disc contains bad sectors. Harddisks are getting older and therefore loose their ability to store data which results in bad sectors. A fs-check would be a good idea also.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900