2084965 - Signal 11 in module proc_decr_pbsharecnt or atomic_cas_32 - SAP ASE

• ASE reports signal 11 in module proc_decr_pbsharecnt or atomic_cas_32
               
• With the affected spid holding the rprocmgr_spin spinlock, it causes ASE to crash.
               
• The ASE errorlog shows log entries including  (offsets will vary by version and platform) :

Current process (hex#) infected with signal 11 (SIGSEGV)
Address hex# (proc_decr_pbsharecnt+0x99)
Spinlocks held by kpid 123456789
Spinlock Resource->rprocmgr_spin at address .....

• When using SAP ASE for Business Suite, the stack trace includes modules:

proc_decr_pbsharecnt+0x99()
showCachedPlanInXml+0x97b()
LeRun+0x5857()

•  When using standalone ASE, a slightly different stack trace can be seen:

proc_decr_pbsharecnt+0x150
showCachedPlanInXml+0x2550
show_cached_plan_in_xml+0xa0

• Another variant of the stacktrace could include :

Current process (0x55002b) infected with signal 11 (SIGSEGV)
Address 0xffffffff7cbba824 (atomic_cas_32), siginfo (code, address) = (1, 0x0000000000000080)

• SAP Adaptive Server Enterprise (ASE) 15.7 SP64, SP100 and higher
• SAP Adaptive Server Enterprise (ASE) 16.0

CR779137, 779137, showCachedPlanInXml, LeRun, show_cached_plan_in_xml, atomic_cas_32 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Bug Filed