On 10/2/07, Chad Leigh -- Shire. Net LLC <[EMAIL PROTECTED]> wrote: > Hi > > In installing trac I ran across a segmentation fault in the initenv > command. > > This seems to be the same problem as shown here: > > http://www.nabble.com/ports-116383%3A-sqlite3-%28from-databases- > sqlite3%29-segfault-tf4449251.html#a12694631 > > Running it in gdb shows > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x50c000 (LWP 100331)] > 0x0000000802f76869 in sqlite3Fts2InitHashTable () from /usr/public/ > lib/libsqlite3.so.8 > (gdb) backtrace > #0 0x0000000802f76869 in sqlite3Fts2InitHashTable () from /usr/ > public/lib/libsqlite3.so.8 > #1 0x0000000802f74f8f in sqlite3Fts2Init () from /usr/public/lib/ > libsqlite3.so.8 > #2 0x0000000802f41be5 in openDatabase () from /usr/public/lib/ > libsqlite3.so.8 > #3 0x0000000802e0bd91 in pysqlite_connection_init () from /usr/ > public/lib/python2.5/site-packages/pysqlite2/_sqlite.so > #4 0x00000008006ab6fb in PyType_IsSubtype () from /usr/public/lib/ > libpython2.5.so.1 > #5 0x000000080066ec83 in PyObject_Call () from /usr/public/lib/ > libpython2.5.so.1 > #6 0x0000000802e09f95 in module_connect () from /usr/public/lib/ > python2.5/site-packages/pysqlite2/_sqlite.so > #7 0x000000080066ec83 in PyObject_Call () from /usr/public/lib/ > libpython2.5.so.1 > #8 0x00000008006dc6da in PyEval_EvalFrameEx () from /usr/public/lib/ > libpython2.5.so.1 > #9 0x00000008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ > libpython2.5.so.1 > #10 0x00000008006888be in PyFunction_SetClosure () from /usr/public/ > lib/libpython2.5.so.1 > #11 0x000000080066ec83 in PyObject_Call () from /usr/public/lib/ > libpython2.5.so.1 > #12 0x00000008006dc272 in PyEval_EvalFrameEx () from /usr/public/lib/ > libpython2.5.so.1 > #13 0x00000008006de336 in PyEval_EvalFrameEx () from /usr/public/lib/ > libpython2.5.so.1 > #14 0x00000008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ > libpython2.5.so.1 > #15 0x00000008006dd9fb in PyEval_EvalFrameEx () from /usr/public/lib/ > libpython2.5.so.1 > #16 0x00000008006dec34 in PyEval_EvalCodeEx () from /usr/public/lib/ > libpython2.5.so.1 > > <rest snipped> > > I do the simple test command as shown in the nabble.com link above > and get basically the same thing > > # gdb sqlite3 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-marcel-freebsd"...(no debugging > symbols found)... > (gdb) r comments.db "CREATE TABLE comments (page, name, email, url, > body);" > Starting program: /usr/public/bin/sqlite3 comments.db "CREATE TABLE > comments (page, name, email, url, body);" > (no debugging symbols found)...(no debugging symbols found)...(no > debugging symbols found)...(no debugging symbols found)...(no > debugging symbols found)...(no debugging symbols found)... > Program received signal SIGSEGV, Segmentation fault. > 0x0000000800698869 in sqlite3Fts2InitHashTable () from /usr/public/ > lib/libsqlite3.so.8 > (gdb) backtrace > #0 0x0000000800698869 in sqlite3Fts2InitHashTable () from /usr/ > public/lib/libsqlite3.so.8 > #1 0x0000000800696f8f in sqlite3Fts2Init () from /usr/public/lib/ > libsqlite3.so.8 > #2 0x0000000800663be5 in openDatabase () from /usr/public/lib/ > libsqlite3.so.8 > #3 0x0000000000403133 in open_db () > #4 0x00000000004053b8 in main () > (gdb) > > Anyone else see this same thing or know about this problem? > > A Google search does not show this mentioned except at the above link. > > Thanks > Chad
Do you have the FTS extension installed? If so, remove it and try again. - Max _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"