3703040 - SIGSEGV caught by VEH_execute that leads to server crash - SAP ASE

• The ASE errorlog reports a 'SIGSEGV caught by VEH_execute'
  
  SIGSEGV is caught by VEH_execute()
  ...
  Return VXACTION_CONTINUE from VEH_execute()
  The Adaptive Server will continue its execution as signal 11 is handled by vectored exception handler
  
  
• Which is followed by subsequent errors that can crash ASE
• Known patterns include:

1. Signal 11 at address s_execute
   Current process (0x44010a9e) infected with signal 11 (SIGSEGV)
   Address 0x0x0000000000fb6e78 (s_execute.cold+0xb4b5), siginfo (code, address) = (2, 0x0x0000000001970d47)
   
   -- with stack functions
   s_execute
   __clock_gettime
   
   -- ASE crashes due to second signal 11 and hits FATAL UNHANDLED EXCEPTION
   Address 0x0x000000000157df37 (proc_release+0x37), siginfo (code, address) = (1, 0x0x0000000000000030)
   FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
   
   -- with stack functions
   proc_release
   s_free
   s_pop
   
   -- or ASE crashed due to spinlock rpmctrl_spin being held
   Spinlocks held by  kpid 12345678
   Spinlock Resource->rpmctrl_spin at address 0x00007f8e88154e00 owned by 12345678
   
   
2. Timeslice with spid holding SSQLCACHE_SPIN
   
   -- errorlog reports timeslice for same spid that hit the first "SIGSEGV is caught by VEH_execute()"
   timeslice -501, current process infected at 0x1ece9b7 (pausenonatomic+0x9)

   -- that spid holds soinlock
   Spinlock SSQLCACHE_SPIN[i] at address 0x00001486ad6c7500 owned by 906560011

   -- with stack functions
   (null)
   ssql_droptext
   procrm
   s_free
   s_pop

SAP Adaptive Server Enterprise (ASE) 16.0 SP04 & 16.1

s_execute.cold+0xb4b5() , __clock_gettime+0x22() , s_execute.cold , proc_release+0x37() , s_free.cold+0x548() , s_free.cold , s_pop+0x146() , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Known Error