SAP Knowledge Base Article - Preview

3316645 - Crash due a stack trace after SIGSEGV is caught by VEH_Optimize - SAP ASE

Symptom

  • Server crashed due the following stack trace:

SIGSEGV is caught by VEH_Optimize()
Return VXACTION_CONTINUE from VEH_Optimize()
server is using elf symbols for stack decoding (131990 symbols found)
Address 0x0x000000000YYYYYbe (Optimize+0x3ca), siginfo (code, address) = (1, 0x0x0000000000000016)
Current process (0x1d3f02f1) infected with signal 11 (SIGSEGV)
...
...
pcstkwalk
ucstkgentrace
ucbacktrace
terminate_process
kisignal
.....
.....
end of stack trace, spid NNN kpid UUUUUU, suid MMMM
Address 0x0x000000000YYYYYdd (rvm_clean_pcrtree+0x4F), siginfo (code, address) = (1, 0x0x00000000deadbni9)
FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
...
kisignal
rvm_clean_pcrtree
....
.....
end of stack trace, spid NNN kpid UUUUUU, suid MMMM
ueshutdown: exiting


Read more...

Environment

Adaptive Server Enterprise 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

SIGSEGV VEH_Optimize() VEH_Optimize  kisignal VXACTION_CONTINUE Optimize VEH crash secondary signal handling rvm_clean_pcrtree 827839 CR 827839 CR827839 CR#827839 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.