2294241 - Signal 11 in mda__traverse_lock_bucket when accessing monLocks table - SAP ASE

• A process accessing the monLocks monitoring table.
• Fails on Unix with "infected with signal 11" or "system exception (0xc0000005)" on Windows in the module mda__traverse_lock_bucket() followed by a stack trace:

Current process (0xe1002a) infected with signal 11 (SIGSEGV)
Address 0x00000000806dc204 (mda__traverse_lock_bucket+0x178)

or

Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation.
kernel  pc: 0x00000000016DB1D5 mda__traverse_lock_bucket+ 0x1b5

• The stack trace includes modules:

mda__traverse_lock_hashtable
mda__read_lock_table
mda_populate_monLocks
mda_exec

• Sometimes ASE will crash as result when the affetced spid is holding a spinlock :

Spinlock fglockspins (or tablockspins) at address ....

SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0

UBFALLOC,  MDA, segmentation, fault, segfault, access, violation, stacktrace , exception, CR796916.CR# 796916. 796916,  CR782871,  CR#782871,  782871 , _$o1cfaoL0.mda__traverse_lock_bucket , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed