SAP Knowledge Base Article - Preview

2014405 - Signal 11 error in pthread_mutex_lock, os_get_prev_stk_desc or _thr_schedctl - SAP ASE

Symptom

  • Client session unexpectedly terminated
  • ASE errorlog contains an 'infected with signal 11 error'
  • With functions, depending on OS, including pthread_mutex_lock, os_get_prev_stk_desc or _thr_schedctl
  • Sample messages from the log will include:

Linux
Current process (0x0) infected with signal 11 (SIGSEGV)
Address ... (pthread_mutex_lock)

with stacktrace including functions:
pthread_mutex_lock
os_get_prev_stk_desc
krtctskException

and may be accompanied by the following message:
comn_signal_event+0x0008: call pthread_mutex_lock [PLT]

Solaris
Current process (0x0) infected with signal 11 (SIGSEGV)
Address 0xffffffff791d1078 (_thr_schedctl+0x7c)

_thr_schedctl
comn_signal_event
ct_async_iopost
np__io_fillbuf_cb
sybnet__do_poll
sybnet__async_poll
thread_create_handler


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

CR697042, 697042, CR#697042, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.