Pro*Fortran Application Throws SIGSEGV (Signal 11) After Upgrade To 11.1.0.7 (Doc ID 1270346.1)

Last updated on JULY 05, 2017

Applies to:

Precompilers - Version 11.1.0.6 to 11.2.0.2 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 05-Feb-2013***

Symptoms

Pro*Fortran application core dumps after the upgrade from Oracle 9.2 to Oracle 11.1.0.7 with the following stack trace:

7cda0824 _kill (ffbfddcc, ffbfd4ec, 1, 2, ffbfd4e8, 7f93447c) + 8
7ed4f04c skgesigCrash (ffbfddc4, 1, 4c8, 6060000, b5ee38, ffbfddc4) + 24
7ed4f70c skgesig_sigactionHandler (b, ffbfea50, ffbfddc8, 6bd9c, 0,
7f934468) + d4
7f9856fc __sighndlr (b, ffbfea50, ffbfe798, 7ed4f638, 0, 0) + c
7f97f354 call_user_handler (b, ffbfea50, ffbfe798, 0, 0, 0) + 234
7f97f504 sigacthandler (b, ffbfea50, ffbfe798, 38, 0, e8) + 64
--- called from signal handler with signal 11 (SIGSEGV) ---
7dda2e10 sqlshv (7f926234, 8, 10b100, ffbfed90, ffbfebb6, 8) + 274
7dda40c8 sqlatm (7f926234, 109c20, 109e40, ffbfed90, 8, 1) + 2e0
7dd900e4 sqlnst (7f926234, 109c20, 25f36, ba, 3, 1430) + 15d4
7dd832b8 sqlcmex (7f926234, c, ffbfed90, 0, 0, 7f6d23e8) + 458
7dd8357c sqlfx7 (1553c, 26054, 8, 1, 5c, 1) + e8
000142fc capture_dispute_ (263a8, 105, 15538, 26264, 26251, 2623c) + 354
000131e4 MAIN_ (262bc, 110, 15394, 800, 7c9ade8c, 800) + 11c
00012a18 ???????? (1, ffbff19c, ffbff1a4, 25800, 0, 0)
000129c0 ???????? (0, 0, 0, 0, 0, 0)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms