Back to: Segmentation Violation

I saw the "Segmentation Violation" threads from earlier but what few /tmp/af.* files were posted didn't look like mine, so here goes: >17:29:13 >17:29:13 Assert Failed: Internal Error - Segmentation Violation >17:29:13 Who: Session(34, nobody@GONZO, 18300, 806729156) > Thread(68, sqlexec, 3013d040, 1) >17:29:13 Results: OnLine must abort >17:29:13 Action: Reinitialize shared memory >17:29:13 See Also: /tmp/af.442ab8, shmem.442ab8.0 >17:29:13 Stack for thread: 68 sqlexec> > base: 0x30602018 > len: 39936 > pc: 0x007e91d4 > tos: 0x3060af78 > >0x007e88d0 mt_affail >0x00698724 rsam_affail >0x004889f8 hang_thread >0x0048880c afsig_segv And that's it in it's entirety! We're running v7.22.UC1 under Irix. I think somebody is trying to update some row when this happens, but I'm still trying to pin it down. This is nasty, hope somebody has ideas... -Chad

In article <19990201181800.01207.00003016@ng-fi1.aol.com>, newhorizon@aol.com (NewHorizon) wrote: > I saw the "Segmentation Violation" threads from earlier but what > few /tmp/af.* files were posted didn't look like mine, so here goes: > > >17:29:13 > >17:29:13 Assert Failed: Internal Error - Segmentation Violation > >17:29:13 Who: Session(34, nobody@GONZO, 18300, 806729156) > > Thread(68, sqlexec, 3013d040, 1) > >17:29:13 Results: OnLine must abort > >17:29:13 Action: Reinitialize shared memory > >17:29:13 See Also: /tmp/af.442ab8, shmem.442ab8.0 > >17:29:13 Stack for thread: 68 sqlexec [cutting]> > This is nasty, hope somebody has ideas... > > -Chad > If you've got the shmem file you might be able to trace the session through to find more information about whats going on Paul Watson # I don't suffer from WF Software Ltd. # stress, I'm just Tel. (+44) 1436 674729 # a carrier Fax. (+44) 1436 678693 # www.wfsoftware.co.uk