In nearly all cases this means you have an eternal inner loop.
Compiling with -debug and let it run will already show you where this happens, so you have an option to check the program.
You may want to compile with -ftrace and set COB_SET_TRACE=1 cobcrun yourprog to inspect this in depth, getting the PERFORMed paragraphs sections.
One question (as this changes the stack change check a bit): is the program RECURSIVE (or "possibly" calls itself, for example via a copybook)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
attempt to reference unallocated memory (signal sigsegv)
compile: cobc -fstack-size=512 duplicate number of records processed
with debug: libcob possible PERFORM depth exceeded
ubuntu 22.04 GnuCOBOL 3.1.2
Will be delighted to get some help... .
In nearly all cases this means you have an eternal inner loop.
Compiling with
-debugand let it run will already show you where this happens, so you have an option to check the program.You may want to compile with
-ftraceand setCOB_SET_TRACE=1 cobcrun yourprogto inspect this in depth, getting thePERFORMed paragraphs sections.One question (as this changes the stack change check a bit): is the program
RECURSIVE(or "possibly" calls itself, for example via a copybook)?