FS#8554 - Gajim SEGFAULT on startup (possibly sqlite3 problem)

Attached to Project: Arch Linux
Opened by Simon Morgan (sjmorgan) - Wednesday, 07 November 2007, 15:01 GMT
Last edited by Isenmann Daniel (ise) - Monday, 12 November 2007, 18:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Simo Leone (neotuli)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7cf86c0 (LWP 22080)]
0xb6b594e7 in sqlite3_step () from /usr/lib/libsqlite3.so.0
(gdb) bt
#0 0xb6b594e7 in sqlite3_step () from /usr/lib/libsqlite3.so.0
#1 0xb6b79b2c in _sqlite_step_with_busyhandler ()
from /usr/lib/python2.5/lib-dynload/_sqlite3.so
#2 0xb6b76534 in cursor_executescript ()
from /usr/lib/python2.5/lib-dynload/_sqlite3.so
#3 0xb7ed038a in PyCFunction_Call () from /usr/lib/libpython2.5.so.1.0
#4 0xb7f1dc5c in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
#5 0xb7f1d792 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
#6 0xb7f1d792 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
#7 0xb7f1f0fb in PyEval_EvalCodeEx () from /usr/lib/libpython2.5.so.1.0
#8 0xb7f1f253 in PyEval_EvalCode () from /usr/lib/libpython2.5.so.1.0
#9 0xb7f41c9a in PyRun_FileExFlags () from /usr/lib/libpython2.5.so.1.0
#10 0xb7f41f9a in PyRun_SimpleFileExFlags ()
from /usr/lib/libpython2.5.so.1.0
#11 0xb7f4226a in PyRun_AnyFileExFlags () from /usr/lib/libpython2.5.so.1.0
#12 0xb7f4badf in Py_Main () from /usr/lib/libpython2.5.so.1.0
#13 0x080485f2 in main ()
This task depends upon

Closed by  Isenmann Daniel (ise)
Monday, 12 November 2007, 18:27 GMT
Reason for closing:  Works for me
Additional comments about closing:  It works on both architectures here without problems.
Comment by Jeff Bailes (thepizzaking) - Saturday, 10 November 2007, 10:56 GMT
Is this the SVN version of gajim? For me it only started happening after revision 8931 http://trac.gajim.org/changeset/8931 . It seems to be caused by CREATE TABLE IF NOT EXISTS, but only in python, running the same script in a sqlite console works without error. A test script which also segfaults can be found here: http://trac.gajim.org/ticket/3515
Comment by Simon Morgan (sjmorgan) - Saturday, 10 November 2007, 15:15 GMT
No. It would be a bit silly of me to file an SVN bug report here. It's in the version that's in extra.
Comment by Sascha Steinbiss (satta2) - Monday, 12 November 2007, 15:48 GMT
Problem still there for me (gajim 0.11.2-1, sqlite3 3.5.2-1, python-pysqlite 2.3.5-1). Which pkg has been updated?
Comment by Andreas Radke (AndyRTR) - Monday, 12 November 2007, 18:08 GMT
[root@workstation64 andyrtr]# pacman -Q gajim
gajim 0.11.2-1 - this one is new and works well here on x86_64.

Loading...