2992794 - Signal 11 in _lopConsWktAccess() when a query with many table UDFs runs - SAP ASE

• Current process infected with signal 11 (SIGSEGV) or Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation may be reported with a stack trace in the module _lopConsWktAccess() when running a query with table user-defined functions (table UDFs) if "inline table functions" configuration parameter is 1.

Current process (0xNNNNN) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000NNNNNN (_lopConsWktAccess(tree*, int, WktDesc**, OptList<Node<Lop>*>&, unsigned char)+0xeb), siginfo (code, address) = (128, 0x(nil))

or

Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation.
pc: 0x0000000000NNNNNN _lopConsWktAccess+ 0x4657b2 (0x000000000933DCE0, 0x00000000000000FD, 0x000000000933DCD0, 0x000000000933DCF0)

• Below is an example of functions reported in the stack trace:

kisignal
_lopConsWktAccess
_lopConsJoins
_lopConsRoot
_lopConsCmds
_lopConsSeq
lopGenerate

SAP Adaptive Server Enterprise (ASE) 16.0

lopConsWktAccess, CR823492, CR#823492, 823492, SEGV, segment, storage, access, violation, fault, segfault, kisignal, stacktrace, Fiori, Monitor Control Status , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Bug Filed