2457953 - Timeslice in tmp__get_tmpobj_by_id() or Signal 11 in open__tempbyname() - SAP ASE15.7

A timeslice or "infected with signal 11" error with a stack can be seen when a JDBC application reuses a temporary table in a dynamically prepared statement.

• The timeslice error is in the function tmp__get_tmpobj_by_id():

timeslice -1501, current process infected at 0x122c82e(tmp__get_tmpobj_by_id+0x2e)

  It is followed by the stack trace that includes functions:

tmp_find_id
open_range
s_opentables
s_mustrecompile
s_execute
sequencer
execproc
tdsrecv__process_batchparam
tdsrecv__dynexec_batch
tdsrecv__dynexec
tdsrecv_dynamic

• The "infected with signal 11" error is in the function open__tempdbbyname():

Current process (0x2e9d0bc7) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000af12e6 (open__tempbyname+0xc6), siginfo (code, address) = (128, 0x(nil))

  It is followed by a stack trace that includes functions:

open__tempbyname
open__byname
open_user_table
builtin_object_id
LeRun
exec_lava
s_execute
sequencer
tdsrecv_language

  Note: Complete stack traces are available under Attachments.

kisignal, stacktrace, segv, temptable, dynamic, CR807625, CR#807625, 807625, segmentation, storage, access, violation, fault, segfault, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed