C program error ... Abort(coredump)

[Ahmed_58]

Dears,
Below messages appear to our apll team, which indicate swap need to be increased,...
---------------------------------------------
Pid 21573 received a SIGSEGV for stack growth failure.Possible causes: insufficient memory or swap space,or stack size exceeded maxssiz.
----------------------------------------------

And after increasing swap file, now below message display, while running C program.

----------------------------------------------
rate_vpn@bat-bcdr:/appl/rate_vpn/bin/rating$ _vpn/bin/cdr/mp/cdr_intermediate --postpaid --tapout --verbose Abort(coredump)
----------------------------------------------

Previously, this program was running withoug any error.

Regards,
Ahmed

[Arunvijai_4]

Hi Ahmed,

Check you have enough memory available in the system with # swapinfo. After that, analyze your program, core with gdb. It could be due to bad programming.

-Arun

[Ahmed_58]

Dear Arun,
Memory seems OK;

# swapinfo -mat
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4096 0 4096 0% 0 - 1 /dev/vg00/lvol2
dev 3424 0 3424 0% 0 - 1 /dev/vg00/lvol10
reserve - 4651 -4651
memory 6513 111 6402 2%
total 14033 4762 9271 34% - 0 -
Regards,
Ahmed

[Dennis Handly]

As Arun says, this is typically due to a programming error. You probably have a recursive stack overflow.

I assume you checked maxssiz and aren't using a Fortran like application that requires a gigantic stack?

If you are now getting SIGABRT and there were no error messages explaining why, you need to get a stack trace then debug the issue. Use gdb's "bt" command:
$ gdb executable core
(gdb) bt
(gdb) q

[Ahmed_58]

I'm not a C programmr, I only OS support, How can I find if maxsiz is the problem? currently it shows :

maxssiz 8388608 8388608 Static maxssiz_64bit 8388608 8388608 Stic maxswapchunks 5473 5473 Static

After I add SWAP space the programmr complining "software that should be working fine is also giving problem"
Kindly help

And they send me below errors;

fill_pabx_imsi|ratebc|070517:14:33|db_functions.c| 733|bcConnectToOracle: serName: 'ADM_RA
TING@TBC15'
fill_pabx_imsi|ratebc|070517 :14:33|db_functions.c| 797|bcConnectToOracle: successful ion.
fill_pabx_imsi|ratebc|070517 10:14:33|read_plmnxref.c| 'NET_PLMN_XREF_A'
fill_pabx_imsi|ratebc|070517 10:14:33|fill_pabx_imsi.c| 264|getImsiFromXRef
fill_pabx_imsi|ratebc|070517 10:14:33|fill_pabx_imsi.c| 265|Statement is-- 'select IMSI from XNET_G
ET_ACT_IMSI_ADM where (MSISDN=:b0 and to_date(:b1,'YYYYMMDDHH24MISS') between (start_date-(1/24)) an
d end_date) order by start_date
h'
fill_pabx_imsi|ratebc|070517 10:14:33|fill_pabx_imsi.c| 266|Function code is 0
fill_pabx_imsi|ratebc|070517 10:14:33|fill_pabx_imsi.c| 269|ORA-00904: "START_DATE": invalid identif
ier

Ahmed

[Dennis Handly · Accepted solution]

>How can I find if maxsiz is the problem? currently it shows: 8388608

8 Mb should be fine. If it was a problem you would still get that SIGSEGV error and not SIGABRT. Unless there is a super special signal handler that prints a message then aborts??

>After I add SWAP space the programmer complining "software that should be working fine is also giving problem"

That programmer will have to debug his application. By using gdb and getting a stack trace may make it obvious.

>And they send me below errors;

Ah, that looked like a jumble of just junk. Until I realized this was wrapped lines that seemed to have some error messages in it.
It would have been better to attach a file with this info, so it doesn't wrap.

Anyway, it is still meaningless to me. Just some error in:
ORA-00904: "START_DATE": invalid identifier

[Ahmed_58]

Dear Dennis,
Thanks for replay... now the programmrs looking into it.
Ahmed