Toad World® Forums

Toad for Sybase producing a lot of Signal 11 errors

Hi All,

In ASE a signal 11 error can be a significant issue causing instability and random re-boots of DBs and ASE - we have noticed in recent times that we are getting an increasing number of signal 11 errors accross our ASE infrastructure.

An observation on this is that almost always its Toad For Syabase connections that seem to generate the signal 11 errors.

There is a stale thread http://www.toadworld.com/products/toad-for-sybase/f/24/t/5220.aspx that talks about this issue but no resolution or any follow up - I would like to request some feedback on this issue and see if there are any explanations and resolutions that anyone is aware of.

ASE Ver: Adaptive Server Enterprise/15.0.3/EBF 18467 ESD#4 ONE-OFF/P/Sun_svr4/OS 5.8/ase1503/2768/64-bit/FBO/Thu Nov 18 20:03:17 2010

Toad Ver: This can vary a bit but:

Toad for Sybase: 1.4.0.1017 (not known to generate this error)

Toad for Sybase: 2.0.1.209 (known to cause this error)

I am following up with the biggest known offender and will update with information once I can get it from them.

Please let me know what further information I can provide - below is the most recent signal 11 error on the ASE env. Some sensitive info has been removed.

07:00000:01289:2014/05/22 10:03:08.12 kernel Current process (0x6a2f0436) infected with signal 11 (SIGSEGV)
07:00000:01289:2014/05/22 10:03:08.13 kernel Address 0x00000000814f569c (GenLavaPhase2+0x2e8), siginfo (code, address) = (1, 0x1b4a959e00000001)
07:00000:01289:2014/05/22 10:03:08.13 kernel Saved signal context address 0x000001002ef9b8e0
07:00000:01289:2014/05/22 10:03:08.13 kernel pc=0x00000000814f569c npc=0x00000000814f56a0
07:00000:01289:2014/05/22 10:03:08.13 kernel g0-g2 0x0000000000000000 0x0000000000030180 0x0000000008002800
07:00000:01289:2014/05/22 10:03:08.13 kernel g3-g5 0x0000000000000020 0x00000000826f2400 0x000001007941e9b4
07:00000:01289:2014/05/22 10:03:08.13 kernel g6-g7 0x0000000000000000 0xffffffff7da00200
07:00000:01289:2014/05/22 10:03:08.13 kernel o0-o2 0x0000010123011f18 0x00000000000000a1 0x000001007941e8f8
07:00000:01289:2014/05/22 10:03:08.13 kernel o3-o5 0x0000000000007c2c 0x00000000000095c8 0x0000010079420350
07:00000:01289:2014/05/22 10:03:08.13 kernel o6-o7 0x000001002ef9b4c1 0x0000000000000000
07:00000:01289:2014/05/22 10:03:08.13 kernel l0-l2 0x1b4a959e00000000 0x0000010135fc7c68 0x0000000081c4ed48
07:00000:01289:2014/05/22 10:03:08.13 kernel l3-l5 0x0000000000200000 0x0000000000009400 0x0000000080000000
07:00000:01289:2014/05/22 10:03:08.13 kernel l6-l7 0x0000000000000002 0x0000000082141c00
07:00000:01289:2014/05/22 10:03:08.13 kernel i0-i2 0x00000101144c2800 0x0000000082141db3 0x0000010000046f40
07:00000:01289:2014/05/22 10:03:08.13 kernel i3-i5 0x0000000000100000 0x0000000000100000 0x0000010123011f58
07:00000:01289:2014/05/22 10:03:08.13 kernel i6-i7 0x000001002ef9b5a1 0x0000000080c43378
07:00000:01289:2014/05/22 10:03:08.13 kernel ************************************
07:00000:01289:2014/05/22 10:03:08.13 kernel SQL causing error : select *
07:00000:01289:2014/05/22 10:03:08.13 kernel ************************************
07:00000:01289:2014/05/22 10:03:08.13 server SQL Text: select *
07:00000:01289:2014/05/22 10:03:08.13 kernel curdb = 8 tempdb = 2 pstat = 0x10000
07:00000:01289:2014/05/22 10:03:08.13 kernel lasterror = 0 preverror = 10331 transtate = 3
07:00000:01289:2014/05/22 10:03:08.13 kernel curcmd = 0 program = Toad for Sybase
07:00000:01289:2014/05/22 10:03:08.13 kernel extended error information: hostname: ####-######### login: USER

Update - the version we are receiving the most number of signal 11 errors from is 2.0.1.209

Bump - this is a fairly serious issue for us, could someone please review and respond.

Hello kcatford,

We recently released version 2.1 with an updated ASE driver. If you get a chance could you please try with the new version and see if you have the same result?

Thanks.