Symptom
- An "Infected with signal 11" error in the module sendtext() or fg_lock() together with a stack trace is reported in the ASE errorlog:
- Current process (...) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000d3019d (sendtext+0x25), siginfo (code, address) = (128, 0x(nil))
- Current process (...) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000af2372 (fg_lock+0x42), siginfo (code, address) = (1, 0x0x0000000000000398)
- The stack trace may include functions:
sendtext
LeSendRow::_sendColsToClient
LeSendRow::sendRowToClient
LeEmitSndOp::_LeOpNext
LePlanNext
exec_lava
Note: An example of a complete stack trace is available under Attachments.
- Error 632 is received along with a stack trace referencing functions, memmove and sendtext
Error: 632, Severity: 20, State: 2
Attempt to move memory with an incorrect length of 28580. Maximum allowed length is 16384. - timeslice / signal error at resd_to_rowfmt reported in ASE errorlog, the stack includes:
kitermproc
(null)
LeEmitSndOp::_LeEoSendRowFormats
LeEmitSndOp::_sendRowFormats
LeEmitSndOp::_LeOpNext
LePlanNext
exec_lava
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 15.7 for Business Suite
- SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
- SAP Adaptive Server Enterprise (ASE) 15.7
- SAP Adaptive Server Enterprise (ASE) 16.0
Product
SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP Solution Manager 7.2
Keywords
memmove, 632, TEXT, CR819416, CR#819416, 819416, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.
SAP Knowledge Base Article - Preview