Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Trac>
  3. Tickets
[The Trac Project] #3790: trac segfault
noreply at edgewall
Sep 26, 2006, 5:23 AM
Post #1 of 9 (4292 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone:
Component: general | Version: 0.10rc1
Severity: normal | Keywords:
--------------------------------+-------------------------------------------
Stack trace

{{{
#0 0xb6da4e40 in sqlite3Pragma () from /usr/lib/libsqlite3.so.0
#1 0xb6da4ee2 in sqlite3Pragma () from /usr/lib/libsqlite3.so.0
#2 0xb6da635a in sqlite3_snprintf () from /usr/lib/libsqlite3.so.0
#3 0xb6db831a in sqlite3VdbeMemStringify () from /usr/lib/libsqlite3.so.0
#4 0xb6db878f in sqlite3ValueText () from /usr/lib/libsqlite3.so.0
#5 0xb6db87c2 in sqlite3ValueBytes () from /usr/lib/libsqlite3.so.0
#6 0xb6db5265 in sqlite3_value_bytes () from /usr/lib/libsqlite3.so.0
#7 0xb6e30ab4 in _fetch_one_row () from /usr/lib/python2.4/site-
packages/pysqlite2/_sqlite.so
#8 0xb6e31dda in cursor_iternext () from /usr/lib/python2.4/site-
packages/pysqlite2/_sqlite.so
#9 0xb6e31e5a in cursor_fetchone () from /usr/lib/python2.4/site-
packages/pysqlite2/_sqlite.so
#10 0x080b61c3 in PyEval_EvalFrame ()
#11 0x080f9441 in PyDescr_NewGetSet ()
#12 0x080b1a36 in PyEval_EvalFrame ()
#13 0x080b580c in PyEval_EvalFrame ()
#14 0x080b580c in PyEval_EvalFrame ()
#15 0x080b580c in PyEval_EvalFrame ()
#16 0x080b726d in PyEval_EvalCodeEx ()
#17 0x080b5719 in PyEval_EvalFrame ()
#18 0x080b580c in PyEval_EvalFrame ()
#19 0x080b580c in PyEval_EvalFrame ()
#20 0x080b580c in PyEval_EvalFrame ()
#21 0x080b726d in PyEval_EvalCodeEx ()
#22 0x080fb6fd in PyFunction_SetClosure ()
#23 0x0805950c in PyObject_Call ()
#24 0x0805eac5 in PyMethod_New ()
#25 0x0805950c in PyObject_Call ()
#26 0x080afed7 in PyEval_CallObjectWithKeywords ()
#27 0x080594e3 in PyObject_CallObject ()
#28 0x080edb2c in init_sre ()
#29 0x080edfbf in init_sre ()
#30 0x080b6a11 in PyEval_EvalFrame ()
#31 0x080b726d in PyEval_EvalCodeEx ()
#32 0x080b5719 in PyEval_EvalFrame ()
#33 0x080b726d in PyEval_EvalCodeEx ()
#34 0x080fb6fd in PyFunction_SetClosure ()
#35 0x0805950c in PyObject_Call ()
#36 0x0805eac5 in PyMethod_New ()
#37 0x0805950c in PyObject_Call ()
#38 0x080b4bf7 in PyEval_EvalFrame ()
#39 0x080b726d in PyEval_EvalCodeEx ()
#40 0x080b5719 in PyEval_EvalFrame ()
#41 0x080b726d in PyEval_EvalCodeEx ()
#42 0x080b5719 in PyEval_EvalFrame ()
#43 0x080b580c in PyEval_EvalFrame ()
#44 0x080b580c in PyEval_EvalFrame ()
#45 0x080b726d in PyEval_EvalCodeEx ()
#46 0x080b5719 in PyEval_EvalFrame ()
#47 0x080b580c in PyEval_EvalFrame ()
#48 0x080b580c in PyEval_EvalFrame ()
#49 0x080b726d in PyEval_EvalCodeEx ()
#50 0x080fb6fd in PyFunction_SetClosure ()
#51 0x0805950c in PyObject_Call ()
#52 0x0805eac5 in PyMethod_New ()
#53 0x0805950c in PyObject_Call ()
#54 0x080afed7 in PyEval_CallObjectWithKeywords ()
#55 0x080594e3 in PyObject_CallObject ()
#56 0x080edb2c in init_sre ()
#57 0x080edfbf in init_sre ()
#58 0x080b6a11 in PyEval_EvalFrame ()
#59 0x080b726d in PyEval_EvalCodeEx ()
#60 0x080b5719 in PyEval_EvalFrame ()
#61 0x080b726d in PyEval_EvalCodeEx ()
#62 0x080b5719 in PyEval_EvalFrame ()
#63 0x080b726d in PyEval_EvalCodeEx ()
#64 0x080b5719 in PyEval_EvalFrame ()
#65 0x080b580c in PyEval_EvalFrame ()
#66 0x080b580c in PyEval_EvalFrame ()
#67 0x080b580c in PyEval_EvalFrame ()
#68 0x080b580c in PyEval_EvalFrame ()
#69 0x080b580c in PyEval_EvalFrame ()
#70 0x080b726d in PyEval_EvalCodeEx ()
#71 0x080fb6fd in PyFunction_SetClosure ()
#72 0x0805950c in PyObject_Call ()
#73 0x0805eac5 in PyMethod_New ()
#74 0x0805950c in PyObject_Call ()
#75 0x0808ac77 in _PyType_Lookup ()
#76 0x0805950c in PyObject_Call ()
#77 0x080b4bf7 in PyEval_EvalFrame ()
#78 0x080b726d in PyEval_EvalCodeEx ()
#79 0x080fb6fd in PyFunction_SetClosure ()
#80 0x0805950c in PyObject_Call ()
#81 0x080b4d37 in PyEval_EvalFrame ()
#82 0x080b726d in PyEval_EvalCodeEx ()
#83 0x080fb6fd in PyFunction_SetClosure ()
#84 0x0805950c in PyObject_Call ()
#85 0x080b4d37 in PyEval_EvalFrame ()
#86 0x080b726d in PyEval_EvalCodeEx ()
#87 0x080fb6fd in PyFunction_SetClosure ()
#88 0x0805950c in PyObject_Call ()
#89 0x080b4d37 in PyEval_EvalFrame ()
#90 0x080b726d in PyEval_EvalCodeEx ()
#91 0x080fb6fd in PyFunction_SetClosure ()
#92 0x0805950c in PyObject_Call ()
#93 0x080b4d37 in PyEval_EvalFrame ()
#94 0x080b580c in PyEval_EvalFrame ()
#95 0x080b726d in PyEval_EvalCodeEx ()
#96 0x080fb6fd in PyFunction_SetClosure ()
#97 0x0805950c in PyObject_Call ()
#98 0x0805eac5 in PyMethod_New ()
#99 0x0805950c in PyObject_Call ()
#100 0x080afed7 in PyEval_CallObjectWithKeywords ()
#101 0x080e013d in _PyObject_GC_NewVar ()
#102 0xb7fc8361 in start_thread () from
/lib/tls/i686/cmov/libpthread.so.0#103 0xb7f34bde in clone () from
/lib/tls/i686/cmov/libc.so.6
}}}

--
Ticket URL: <http://trac.edgewall.org/ticket/3790>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 26, 2006, 5:27 AM
Post #2 of 9 (4204 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Changes (by cboos):

* keywords: => pysqlite
* owner: jonas => cboos
* severity: normal => major
* priority: normal => high

Comment:

Well, pysqlite2 segfaulted...

So the usual questions:
- what version of PySqlite?
- what version of SQLite?
- was PySqlite built with the `--enable-threadsafe` configuration switch
set?

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:1>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 26, 2006, 5:29 AM
Post #3 of 9 (4183 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Comment (by cboos):

Replying to [comment:1 cboos]:
> - was PySqlite built with the `--enable-threadsafe` configuration
switch set?
Sorry I meant ''SQLite'' in the above.
Also, where other configuration options used?

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:2>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 26, 2006, 5:31 AM
Post #4 of 9 (4209 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Comment (by cboos):

Replying to [comment:1 cboos]: > - was PySqlite built with the `--enable-
threadsafe` configuration switch set? Sorry I meant ''SQLite'' in the
above. Also, were other configuration options used?

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:2>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 26, 2006, 11:01 AM
Post #5 of 9 (4194 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Changes (by exarkun@divmod.com):

* cc: exarkun@divmod.com (added)

Comment:

* SQLite 3.2.1
* PySQLite 2.0.3
* SQLite was built with {{{--enable-threadsafe}}}. The only other
configure parameter was {{{--with-tcl=/usr/lib/tcl8.4}}}. {{{CFLAGS}}}
was also set to {{{-g -Wall -O2 -fno-strict-aliasing}}}

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:3>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 26, 2006, 2:20 PM
Post #6 of 9 (4187 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Comment (by cboos):

Well, that SQLite version is nearly
[http://www.sqlite.org/cvstrac/timeline?d=550&e=2006-Sep-
26&c=2&px=sqlite%2Fsrc%2Fprintf.c&s=0&dm=1&x=1&m=1 2 years old].
It's most probably a bug there, in printf.c. Try upgrading to 3.3.7 (and
PySqlite 2.3.2 at that occasion).

The configuration you used was ok.

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:4>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Sep 30, 2006, 8:47 PM
Post #7 of 9 (4163 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Comment (by anonymous):

I've upgraded. I'll comment again if I see the problem again.

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:5>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Oct 5, 2006, 3:42 PM
Post #8 of 9 (4180 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite |
--------------------------------+-------------------------------------------
Comment (by exarkun@divmod.com):

Another segfault - different backtrace, however:

{{{
#0 0xb6c1912b in svn_error_clear (err=0x2f) at
subversion/libsvn_subr/error.c:273
#1 0xb6a35988 in svn_fs_bdb__wrap_db (fs=0x8b98fc0, operation=0xb6a4e02f
"opening 'nodes' table", db_err=0)
at subversion/libsvn_fs_base/bdb/bdb-err.c:93
#2 0xb6a3e006 in open_databases (fs=0x8b98fc0, create=0, path=0x8b98ac0
"/home/trac/svn/Twisted/db", pool=0x8b987c0)
at subversion/libsvn_fs_base/fs.c:559
#3 0xb6a3e468 in base_open (fs=0x8b98fc0, path=0xb7ebc938 "",
pool=0x8b987c0) at subversion/libsvn_fs_base/fs.c:685
#4 0xb7692a11 in svn_fs_open (fs_p=0x8b98a80, path=0x8b98ac0
"/home/trac/svn/Twisted/db", fs_config=0x0, pool=0x8b987c0)
at subversion/libsvn_fs/fs-loader.c:367
#5 0xb6a1434d in get_repos (repos_p=0xb21fa57c, path=Variable "path" is
not available.
) at subversion/libsvn_repos/repos.c:1803
#6 0xb68cf394 in _wrap_svn_repos_open (self=0x0, args=0x8d2284c) at
./subversion/bindings/swig/python/svn_repos.c:2047
#7 0x0805950c in PyObject_Call ()
#8 0x080afed7 in PyEval_CallObjectWithKeywords ()
#9 0x080a88ed in _PyUnicodeUCS4_IsNumeric ()
#10 0x080b6a11 in PyEval_EvalFrame ()
#11 0x080b726d in PyEval_EvalCodeEx ()
#12 0x080b5719 in PyEval_EvalFrame ()
#13 0x080b726d in PyEval_EvalCodeEx ()
#14 0x080fb6fd in PyFunction_SetClosure ()
#15 0x0805950c in PyObject_Call ()
#16 0x0805eac5 in PyMethod_New ()
#17 0x0805950c in PyObject_Call ()
#18 0x0808a965 in _PyType_Lookup ()
#19 0x0808ca88 in _PyObject_SlotCompare ()
#20 0x0805950c in PyObject_Call ()
#21 0x080b4bf7 in PyEval_EvalFrame ()
#22 0x080b580c in PyEval_EvalFrame ()
#23 0x080b580c in PyEval_EvalFrame ()
#24 0x080b726d in PyEval_EvalCodeEx ()
#25 0x080b5719 in PyEval_EvalFrame ()
#26 0x080b580c in PyEval_EvalFrame ()
#27 0x080b580c in PyEval_EvalFrame ()
#28 0x080b580c in PyEval_EvalFrame ()
#29 0x080b580c in PyEval_EvalFrame ()
#30 0x080b726d in PyEval_EvalCodeEx ()
#31 0x080fb6fd in PyFunction_SetClosure ()
#32 0x0805950c in PyObject_Call ()
#33 0x0805eac5 in PyMethod_New ()
#34 0x0805950c in PyObject_Call ()
#35 0x0808ac77 in _PyType_Lookup ()
#36 0x0805950c in PyObject_Call ()
#37 0x080b4bf7 in PyEval_EvalFrame ()
#38 0x080b726d in PyEval_EvalCodeEx ()
#39 0x080fb6fd in PyFunction_SetClosure ()
#40 0x0805950c in PyObject_Call ()
#41 0x080b4d37 in PyEval_EvalFrame ()
#42 0x080b726d in PyEval_EvalCodeEx ()
#43 0x080fb6fd in PyFunction_SetClosure ()
#44 0x0805950c in PyObject_Call ()
#45 0x080b4d37 in PyEval_EvalFrame ()
#46 0x080b726d in PyEval_EvalCodeEx ()
#47 0x080fb6fd in PyFunction_SetClosure ()
#48 0x0805950c in PyObject_Call ()
#49 0x080b4d37 in PyEval_EvalFrame ()
#50 0x080b726d in PyEval_EvalCodeEx ()
#51 0x080fb6fd in PyFunction_SetClosure ()
#52 0x0805950c in PyObject_Call ()
#53 0x080b4d37 in PyEval_EvalFrame ()
#54 0x080b580c in PyEval_EvalFrame ()
#55 0x080b726d in PyEval_EvalCodeEx ()
#56 0x080fb6fd in PyFunction_SetClosure ()
#57 0x0805950c in PyObject_Call ()
#58 0x0805eac5 in PyMethod_New ()
#59 0x0805950c in PyObject_Call ()
#60 0x080afed7 in PyEval_CallObjectWithKeywords ()
#61 0x080e013d in _PyObject_GC_NewVar ()
#62 0xb7eed361 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#63 0xb7e59bde in clone () from /lib/tls/i686/cmov/libc.so.6
}}}

Versions of software now being used:

* SQLite 3.3.7
* PySQLite 2.3.2
* Subversion 1.4.0
* APR 0.9.12 (included with svn 1.4.0 utils)
* APR Utils 0.9.12 (included with svn 1.4.0 utils)

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:6>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
Re: [The Trac Project] #3790: trac segfault [ In reply to ]
noreply at edgewall
Oct 5, 2006, 10:56 PM
Post #9 of 9 (4193 views)
Permalink
#3790: trac segfault
--------------------------------+-------------------------------------------
Reporter: exarkun@divmod.com | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: 0.10rc1
Severity: major | Resolution:
Keywords: pysqlite svn crash |
--------------------------------+-------------------------------------------
Changes (by cboos):

* keywords: pysqlite => pysqlite svn crash

Comment:

Replying to [comment:6 exarkun@divmod.com]:
> Another segfault - different backtrace, however:
>
> [[br]]
> `#0 0xb6c1912b in svn_error_clear (err=0x2f) at
subversion/libsvn_subr/error.c:273` [[br]]
> `#1 0xb6a35988 in svn_fs_bdb__wrap_db (fs=0x8b98fc0,
operation=0xb6a4e02f \` [[br]]
> `"opening 'nodes' table", db_err=0) at
subversion/libsvn_fs_base/bdb/bdb-err.c:93` [[br]]
> ...

> Versions of software now being used:
>
> * SQLite 3.3.7
> * PySQLite 2.3.2
Good!

> * Subversion 1.4.0
> * APR 0.9.12 (included with svn 1.4.0 utils)
> * APR Utils 0.9.12 (included with svn 1.4.0 utils)
The crash involves `svn_fs_bdb__wrap_db`, so I bet there's an
incompatibility between the BDB version expected by the APR (APR utils I
think) you're using and the BDB lib that ends up being used.

Don't bother checking out the details and do yourself a favor by migrating
to fsfs ;) (see TracSubversion#TracandSubversion1.2)

--
Ticket URL: <http://trac.edgewall.org/ticket/3790#comment:7>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal