3357731 - Stack trace with signal 11 in open_table or optimize in tabvar_release - SAP ASE

• Stack trace with signal 11 reported when executing an insert into table variable selecting data from another table, for example:
  INSERT INTO @tabvar (xxxxxxx) SELECT yyyyyyyyy FROM tb01
• The first stack trace related to this issue is the following:
  Address 0x0x000000000xxxxxxx (open_range+0x111), siginfo (code, address) = (1, 0x0x0000zzzzzzzzz)
  Current process (0x9ppppp) infected with signal 11 (SIGSEGV)
  kisignal
  open_range
  open_one_side
  s_preprocess
  s_compile
  sequencer
  execproc
  execrpc
  
  Address 0x0x00000000001111e (tabvar_release+0x78), siginfo (code, address) = (1, 0x0x00007fdc869d9999)
  FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
  kisignal
  tabvar_release
  tmp_alldrop
  s_free
  
  
  
• The second stack trace that can be reported is the following:
  SIGSEGV is caught by VEH_Optimize
  Return VXACTION_CONTINUE from VEH_Optimize
  Address 0x0x000000000yyyyyyy (Optimize+0x11f), siginfo (code, address) = (1, 0x(nil))
  Current process (0x11111cb) infected with signal 11 (SIGSEGV)
  kisignal
  
  Address 0x0x0000000000yyyyy (tabvar_release+0x78), siginfo (code, address) = (1, 0x0x0000yyyyyyyyy)
  Task is made zombie due to unsuccessful clean up during its termination, kpid 11111111, state 1. This task may have resources allocated to it.
  

SAP Adaptive Server Enterprise (ASE) 16.0

 select table, variable 828237, CR 828237, CR828237, CR#828237 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Known Error