cancel
Showing results for 
Search instead for 
Did you mean: 

Signal 11 stack trace on ASE SP122

0 Kudos

Hi

Please advise if anyone encountered below signal 11 stack trace

- Sybase server Config : ASE SP122 , pagesize 8K, all tables are having datarows locking

- No parameter reached up to threshold in sp_monitorconfig “all”

- Nothing recorded in sysmon report

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  Current process (0x817011d) infected with signal 11 (SIGSEGV)

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  Address 0x0x0000000000873006 (LeDataRow::LeDataRow(LeVtuple*, LeDRRowType, int, proc_hdr*, int, sdes*, int, int)+0x166), siginfo (code, address) = (1, 0x0x00000000000000d2)

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  **** Saved signal context (0x0x00002aaacb74c400): ****

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  uc_flags: 0x0, uc_link: 0x(nil)

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  uc_sigmask: 0x416000 0xb 0x1 0xd2

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  General Registers (uc_mcontext.gregs):

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       PC : 0x0000000000873006 (LeDataRow::LeDataRow(LeVtuple*, LeDRRowType, int, proc_hdr*, int, sdes*, int, int)+0x166)

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel          RAX : 0x00002aab4258c148  RBX : 0x00002aab4258e7d8

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel          RCX : (nil)  RDX : (nil)

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       RBP : 0x00002aaacb74c880  RSP : 0x00002aaacb74c840

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       R8  : 0x00002aab4258c0c8  R9  : 0x0000000000000002

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       R10 : 0x0000000000000001  R11 : 0x00002aaaaac20840

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       R12 : 0x000000000000000f  R13 : 0x0000000000000002

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       R14 : 0x0000000000000003  R15 : 0x00002aab4258c070

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       RDI : 0x0000000002a581c8  RSI : 0x00002aab4258c0d0

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       RIP : 0x0000000000873006  CSGSFS : 0x2020000000000033

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       TRAPNO : 0x000000000000000e  ERR : 0x0000000000000004

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel       EFL : 0x0000000000010202

00:0008:00000:00376:2015/08/18 18:38:23.13 kernel  **** end of signal context ****

00:0008:00000:00376:2015/08/18 18:38:23.13 server  Initiating shared memory dump for signal 11.

00:0008:00000:00376:2015/08/18 18:38:23.14 kernel  Dumping shared memory to dump file: /data/sybase_dumps/memdumps/SAASDEV22.dmp.2015081818382302

00:0008:00000:00376:2015/08/18 18:38:23.14 kernel  Writing segment 0:

00:0008:00000:00376:2015/08/18 18:38:23.14 kernel  Thread (0): Writing 3059843072 bytes starting at 0x0x2aaaaac00000

00:0008:00000:00376:2015/08/18 18:38:51.91 kernel  Writing segment 1:

00:0008:00000:00376:2015/08/18 18:38:51.91 kernel  Thread (0): Writing 479109120 bytes starting at 0x0x2aaf0aa18000

00:0008:00000:00376:2015/08/18 18:38:54.72 kernel  Writing segment 2:

00:0008:00000:00376:2015/08/18 18:38:54.72 kernel  Thread (0): Writing 32571392 bytes starting at 0x0x2aaf67302000

00:0008:00000:00376:2015/08/18 18:38:54.74 kernel  Writing segment 3:

00:0008:00000:00376:2015/08/18 18:38:54.74 kernel  Thread (0): Writing 8052736 bytes starting at 0x0x2aaf78c12000

00:0008:00000:00376:2015/08/18 18:38:54.75 kernel  Writing segment 4:

00:0008:00000:00376:2015/08/18 18:38:54.75 kernel  Thread (0): Writing 32174080 bytes starting at 0x0x2aafb7bc0000

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Writing segment 5:

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Thread (0): Writing 16384 bytes starting at 0x0x2aafb9c6f000

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Writing segment 6:

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Thread (0): Writing 933888 bytes starting at 0x0x2aafba477000

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Writing segment 7:

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel  Thread (0): Writing 4096 bytes starting at 0x0x2ab0eabff000

00:0008:00000:00376:2015/08/18 18:38:54.77 kernel

Copying errorlog into dump file.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Answers (1)

Answers (1)

0 Kudos

Our stored procedure was having approx 3500 lines of code and had 99  “UNION ALL” statements means 100 tables were being used to generate the stored procedure resultset. Here a small modification I have done that to trim down the union statement resultset after inserting one more “INSERT INTO” statement for last two select statements. Likewise SP functionality and results would be the same and overcame the issue.