3587168 - Signal 11 happened from routine concat - SAP ASE

• signal 11 happened at rtrim or null() module.
  
  Case 1)
  
  kernel  Address 0x00000001026af4b8 (rtrim+0x50)
  kernel  Current process (0x6bbf017d) infected with signal 11 (SIGSEGV)
  (omit)
  kernel  pc: 0x0000000101b52dc8 kisignal.fdpr.chunk
  kernel  pc: 0x00000001026af4b8 rtrim
  kernel  pc: 0x00000001026af3e8 LeRun.fdpr.chunk
  kernel  pc: 0x000000010245c578 LeEvals::LeEvRun
  kernel  pc: 0x00000001024c1cb0 LeRestrictOp::_LeOpOpen
  
  Case 2)
  kernel  pc: 0x0000000101b52dc8 kisignal.fdpr.chunk
  kernel  pc: 0x000000000000f49c ()
  kernel  pc: 0x000000010245fe58 LeRun.fdpr.chunk
  kernel  pc: 0x000000010245c578 LeEvals::LeEvRun
  kernel  pc: 0x00000001024c1cb0 LeRestrictOp::_LeOpOpen
  
  
• When reproducing the issue under diagserver mode, the signal 11 happened at concat module.
  
  kernel  pc: 0x00000000032d780e kisignal
  kernel  pc: 0x00007f498f8dfc13 (null)
  kernel  pc: 0x000000000188d80b concat
  kernel  pc: 0x0000000000edd589 LeRun
  kernel  pc: 0x0000000000ea908e LeEvals::LeEvRun
  
  
• The query in question sometimes returned 0 row without an error.

SAP Adaptive Server Enterprise (ASE) 16.0

signal 11, SIGSEGV, SAP ASE error log, SELECT query, LIKE clause, stack trace, CR830521, 830521, CR#830521, alternative_greedy_search, statement_cache, enable literal autoparam, dbcc traceon , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem