Re: Segmentation Violation (bad memory pointer)

Lutz Wiggershaus schrieb in Nachricht <72rf9u$7gt$1@goof.de.uu.net>... > >SaTriGuy schrieb in Nachricht ><19981117010902.11351.00001616@ng23.aol.com>... >>We really need the contents of the af.xxx file to begin to diagnoise a >>problem. >>M >Unfortunately the af-File only contains a few unprintable chracters and a >part of the online.log-File, >here is the hex-dump of the beginning and the end of the file: We now have an af-file from a second crash: 24:10:16 24:10:16 Assert Failed: Internal Error - Segmentation Violation 24:10:16 Who: Session(3663, hel3@bdv50001, 17406, 382102364) Thread(3705, sqlexec, 16c4bd38, 1) 24:10:16 Results: OnLine must abort 24:10:16 Action: Reinitialize shared memory 24:10:16 See Also: /tmp/af.e79796b, shmem.e79796b.0 24:10:16 Stack for thread: 3705 sqlexec base: 0x174de014 len: 36864 pc: 0x00271fa1 tos: 0x174e6284 0x174e62e8 ***unknown*** (0x1717d47c, 0x2e407000, 0x43e348, 0x16c4bd38) 0x002719ce mt_affail (0x170bdecc, 0x1730da08, 0x170bdf0c, 0x16c4bd38) 0x0019dac1 rsam_affail (0x170bdecc, 0x1730da08, 0x170bdf0c, 0x16c4bd38) 0x00010537 hang_thread (0x40261c, 0x170bdecc, 0xb, 0x174e6be8) 0x000103ff afsig_segv (0xb, 0x171f0000, 0x0, 0x49001f) 0x003a0178 _sigismember (0x171b65e8, 0x171f5c08, 0x174e6d7c, 0x174e6d74) 0x0005073d readidx (0x171b65e8, 0x100, 0x174e6e06, 0x0) 0x000500aa gettupl (0x171b65e8, 0x0, 0x0, 0x171b6474) 0x0004eb42 scan_next (0x171b65e8, 0x0, 0x172082f0, 0x17208028) 0x0005ccb3 sort_open (0x171b6474, 0x4847b0, 0x3, 0x17208028) 0x0005311c prepselect (0x17208028, 0x400850, 0x3, 0x6) 0x000c2514 open_cursor (0x174e6ff8, 0xd068b, 0x0, 0x4849c4) 0x000c2105 sq_open (0x0, 0x4849c4, 0xa, 0x170c7024) 0x000d068b sqmain (0x0, 0x0, 0x0, 0x0) 0x0025c270 startup (0xffffffff, 0x174f2000, 0x174de000, 0xfec) 0x00000000 ***unknown*** 24:10:17 ------------------ End of assertion failure 0 -----------------