3703040 - SIGSEGV caught by VEH_execute followed by s_execute which can crash server - SAP ASE

• The ASE errorlog reports
  • a 'SIGSEGV caught by VEH_execute'
  • followed by a signal 11 at address s_execute 
  • which can crash the server due to FATAL UNHANDLED EXCEPTION or Spinlock Resource->rpmctrl_spin
• Typical log entries include
  
  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
  
  Current process (0x44010a9e) infected with signal 11 (SIGSEGV)
  Address 0x0x0000000000fb6e78 (s_execute.cold+0xb4b5), siginfo (code, address) = (2, 0x0x0000000001970d47)
  
  -- stack functions
  s_execute
  __clock_gettime
  
  
• ASE crashes due to
  
  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.
  
  -- stack functions
  proc_release
  s_free
  s_pop
  
  or 
  
  Spinlocks held by  kpid 12345678
  Spinlock Resource->rpmctrl_spin at address 0x00007f8e88154e00 owned by 12345678

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 , Bug Filed