Symptom
-
ASE 15.7 and ASE 16.0 reports Signal 11 with a stack trace in the module _lopConsWktAccess() when running a query with JOINs and UNION ALL:
Current process (0x450023) infected with signal 11 (SIGSEGV)
Address 0x0000000080a18890 (Node <Lop>*_lopConsWktAccess(tree*,int,WktDesc**,OptList<Node<Lop>*>&)+0x138), siginfo (code, address) = (1, 0x0000000000000010)
-
This is an example of functions reported in the stack trace:
Node<Lop>*_lopConsWktAccess(tree*,int,WktDesc**,OptList<Node<Lop>*>&)
Node<Lop>*_lopConsJoins(tree*,WktDesc**,OptList<Node<Lop>*>&,OneTimeCopy&)
Node<Lop>*_lopConsRoot(tree*,WktDesc**,OptList<Node<Lop>*>&,OptMap<tree*,Node<Lop>*,_STL::less<tree*> >&,OneTimeCopy&)
Node<Lop>*_lopConsCmds(tree*,WktDesc**,OptMap<tree*,Node<Lop>*,_STL::less<tree*> >&,OneTimeCopy&)
Node<Lop>*_lopConsUnion(tree*,WktDesc**,OneTimeCopy&)
Node<Lop>*_lopConsSeq(tree*,OneTimeCopy&)
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 15.7
- SAP Adaptive Server Enterprise (ASE) 16.0
Product
Keywords
lopConsWktAccess, OptList<Node, CR786753, CR#786753, 786753, SEGV, segment, storage, access, violation, fault, segfault, kisignal, stacktrace , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.