On Wed, 26 Apr 2006, Daniel Swarbrick wrote: > On Mon, 2006-04-10 at 13:37 +0200, Armin Schindler wrote: > > > On Mon, 10 Apr 2006, Daniel Swarbrick wrote: > > > Armin Schindler wrote: > > > > > > > > I tried new pre-0.2 now and the problem still exist. After 5 days of > > > > perfect > > > > run, the segfault happens at the same place again: > > > > So I think the problem is sqlite. > > > > I think of moving to another database. Does anyone uses mysql? > > > > > > I just had a segfault on a box I upgraded from svn-1540 to svn-1553. > Previously it had been running flawlessly on svn-1540, but we also run > svn-1553 in our office, with no issues. The backtrace would appear to > indicate the crash occurred in sqlite3Malloc(): > > (gdb) bt > #0 0xb7ceb82f in free () from /lib/tls/libc.so.6 > #1 0xb7cecdfc in malloc () from /lib/tls/libc.so.6 > #2 0xb7a245da in sqlite3Malloc (n=-1210345224) at src/util.c:296 > #3 0xb7a2d070 in sqlite3VdbeMakeReady (p=0x8158998, nVar=0, nMem=4, ... > This looks similar to the backtrace Armin posted a couple of weeks ago.
I rechecked all the backtraces from the segfaults I get about twice a week. It is always related to sqlite functions which calls any libc functions with a wrong pointer. Armin _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
