SAP Knowledge Base Article - Preview

2688931 - ASE infected with Signal 11 (SIGSEGV) when printing query execution info or final plan in XML - SAP ASE

Symptom

  • An "infected with signal 11"  reported in the ASE errorlog
  • Which can be seen at "Address" functions: si_code, ExeCtxt::printXMLCostMetrics or GenLavaPhase2
  • The ASE errorlog shows entries like
     
    Current process (0x1edd06e3) infected with signal 11 (SIGSEGV)
    Address 0x40a9080000000000 (si_code: 0x1, si_addr: 0x40a9080000000000) or
    Address 0x0x0000000000dcb9ba (GenLavaPhase2+0x52a) ...

    followed by a stack trace which includes modules:

    _ZN8TraceOut11startXMLDocEPKc9QpDocType
    GenLavaPhase2

or

Current process (0x1edd06e3) infected with signal 11 (SIGSEGV)
Address 0x000000008062052c (void ExeCtxt::printXMLCostMetrics()const+0x10)

followed by a stack trace which includes modules:

TraceOut::startXMLDoc
ExeCtxt::printXMLCostMetrics
LeProcessExecStats
LePlanRelease

  • The client was running the Toad for Data Analysts program as printed in the stack trace:

program = Toad for Sybase


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.0.3, 15.5 and 15.7

Product

SAP Adaptive Server Enterprise 15.7 ; Sybase Adaptive Server Enterprise 15.5

Keywords

SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers, CR709255, CR#709255, CR709255 , printXMLCostMetrics , 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.