SAP Knowledge Base Article - Preview

2633304 - Signal 10 or 11 in ktMuxThreadScheduleOut() with stack overflow crashing the server - SAP ASE


  • ASE hits a signal 10 or 11 in the module ktMuxThreadScheduleOut() followed by a stack trace:

Current process (0x68750f94) infected with signal 10 (SIGBUS)
Address 0x0000000081622934 (ktMuxThreadScheduleOut+0x44)

  • And in handling the signal error ASE hits a stack overflow.
  • The stack trace(s) contains numerous stack / error handling functions and messages including:


Stack overflow detected: limit: 0x00000100334f09f0, guardpage: 0x00000100334f99f0, sp: 0x0000010033575e9c
*** Stack guardword corrupted.
*** Stack corrupted, server aborting.

pcstkwalk: exception stack underflow occurred.

  • This casues the ASE server crash:

ueshutdown: exiting



SAP Adaptive Server Enterprise (ASE) 16.0.

** Only reported on SP01 PL02 on Solaris 10, but it is possible that other versions and/or platforms are affected.


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0


CR813598, CR#813598, 813598, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, 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.