SIGSEGV Errors

[John Walker_1]

Has anyone ever had a problem with SIGSEGV messages caused by the
identification division of a COBOL source being incorrect, for example, the words
IDENTIFICATION DIVISION missing or the PROGRAM-ID clause not matching the
source filename?

[harry d brown jr]

without an ID Div you aren't going too far with COBOL (flash backs to those years of writing COBOL programs).

I guess what I'm saying is that I'm not too clear on your issue?

live free or die
harry

[John Walker_1]

One of our applications is causing core dumps which report the SIGSEGV error. This is often related to stack growth failures and various kernel parameter settings like maxssiz etc.
A previous similar error was giving these messages but was resolved by rectifying the Cobol stuff I originally mentioned.
I was just wondering if it was a common issue that someone else may have heard of.

[Paula J Frazer-Campbell]

Hi

Have a look at maxfiles.

Paula

[John Walker_1]

Paula

All relevant kernel parameters have already been checked and amended where necessary but the core files still get generated with a SIGSEGV error.

[AUJ]

I encounter the same problem on the SIVSEG error in my locally develop program; increase the kernel related parameters like maxdsiz, maxtsiz and maxssiz almost to the MAX but problem still exist and finally found that problem causing the error was the libc cumulative patch. After removing the patch temporarily, the program run perfectly. Double check the patch level installed in your system, that might caused the problem also.

[Paula J Frazer-Campbell]

John
Does it dump a core file?

Paula

[Chris Lonergan]

John

SIGSEGV is a segmentation violation caused by a program trying to access memory outside of it's allocation.

Of the errors you mention, no ID DIVISION would not compile, the PROGRAM-ID does not have to match the sourcefile name but it is prudent to keep them the same.

Try checking that items in the LINKAGE SECTION are the same size in all sourcefiles and that the USING statement in all call/called sourcefiles have the data-names in the same sequence.

Other potential, but less common causes are the use of pointers that get initialised to an 'out of bounds' value and the EXTERNAL clause.

Hope this helps

Chris