338228 – net-p2p/deluge seems to fail with latest cairo-1.10.0-r3

Bug 338228 - net-p2p/deluge seems to fail with latest cairo-1.10.0-r3

Summary: net-p2p/deluge seems to fail with latest cairo-1.10.0-r3

Status:	RESOLVED TEST-REQUEST

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo net-p2p team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-09-20 20:32 UTC by Joost Ruis
Modified:	2012-04-22 16:18 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Joost Ruis 2010-09-20 20:32:47 UTC

joost@xbox-360 ~ $ deluge
Segmentation fault


joost@xbox-360 ~ $ gdb --args python /usr/bin/deluge
GNU gdb (Gentoo 7.1 p1) 7.1
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/python /usr/bin/deluge
process 8504 is executing new program: /usr/bin/python2.6
[Thread debugging using libthread_db enabled]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2400.1-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[New Thread 0x7fffe2dca910 (LWP 8511)]
[New Thread 0x7fffe25c9910 (LWP 8512)]
[Thread 0x7fffe25c9910 (LWP 8512) exited]
[New Thread 0x7fffe25c9910 (LWP 8513)]
[New Thread 0x7fffe0ae3910 (LWP 8514)]
[New Thread 0x7fffdbfff910 (LWP 8515)]
[New Thread 0x7fffdb7fe910 (LWP 8516)]

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe962a1d4 in __cxa_allocate_exception () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.2/libstdc++.so.6


Reproducible: Always

Comment 1 Joost Ruis 2010-09-20 20:36:18 UTC

(gdb) bt
#0  0x00007fffe962a1d4 in __cxa_allocate_exception () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.2/libstdc++.so.6
#1  0x00007fffe114ba4e in boost::python::throw_error_already_set() () from /usr/lib/libboost_python-mt-1_41.so.1.41.0
#2  0x00007fffe1a73d1d in boost::python::api::object_operators<boost::python::api::proxy<boost::python::api::attribute_policies> >::operator()() const () from /usr/lib64/python2.6/site-packages/libtorrent.so
#3  0x00007fffe1a766f6 in prioritize_files(libtorrent::torrent_handle&, boost::python::api::object) () from /usr/lib64/python2.6/site-packages/libtorrent.so
#4  0x00007fffe1a7de4e in boost::python::objects::caller_py_function_impl<boost::python::detail::caller<void (*)(libtorrent::torrent_handle&, boost::python::api::object), boost::python::default_call_policies, boost::mpl::vector3<void, libtorrent::torrent_handle&, boost::python::api::object> > >::operator()(_object*, _object*) () from /usr/lib64/python2.6/site-packages/libtorrent.so
#5  0x00007fffe1144336 in boost::python::objects::function::call(_object*, _object*) const () from /usr/lib/libboost_python-mt-1_41.so.1.41.0
#6  0x00007fffe1144518 in ?? () from /usr/lib/libboost_python-mt-1_41.so.1.41.0
#7  0x00007fffe114bbbb in boost::python::handle_exception_impl(boost::function0<void>) () from /usr/lib/libboost_python-mt-1_41.so.1.41.0
#8  0x00007fffe1141058 in ?? () from /usr/lib/libboost_python-mt-1_41.so.1.41.0
#9  0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#10 0x00007ffff7b185fe in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#11 0x00007ffff7b19103 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#12 0x00007ffff7b19103 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#13 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#14 0x00007ffff7aad0a0 in ?? () from /usr/lib/libpython2.6.so.1.0
#15 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#16 0x00007ffff7a97d1f in ?? () from /usr/lib/libpython2.6.so.1.0
#17 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#18 0x00007ffff7ad7f5e in ?? () from /usr/lib/libpython2.6.so.1.0
#19 0x00007ffff7ad6b78 in ?? () from /usr/lib/libpython2.6.so.1.0
#20 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#21 0x00007ffff7b185fe in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#22 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#23 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#24 0x00007ffff7b19103 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#25 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#26 0x00007ffff7aad19d in ?? () from /usr/lib/libpython2.6.so.1.0
#27 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#28 0x00007ffff7b17505 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
---Type <return> to continue, or q <return> to quit---
#29 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#30 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#31 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#32 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#33 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#34 0x00007ffff7aad19d in ?? () from /usr/lib/libpython2.6.so.1.0
#35 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#36 0x00007ffff7b17505 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#37 0x00007ffff7b19103 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#38 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#39 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#40 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#41 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#42 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#43 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#44 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#45 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#46 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#47 0x00007ffff7aad19d in ?? () from /usr/lib/libpython2.6.so.1.0
#48 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#49 0x00007ffff7b17505 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#50 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#51 0x00007ffff7aad19d in ?? () from /usr/lib/libpython2.6.so.1.0
#52 0x00007ffff7a850d3 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#53 0x00007ffff7b17505 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#54 0x00007ffff7b19103 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#55 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#56 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#57 0x00007ffff7b1a648 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#58 0x00007ffff7b188db in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0

I also want to stress that when I revert to previous cairo version the program runs just fine.

Comment 2 Joost Ruis 2010-09-21 16:23:53 UTC

Today I recompiled cairo without qt4 flag and deluge instantly worked again.

Comment 3 Raúl Porcel (RETIRED) gentoo-dev

2010-10-02 15:24:40 UTC

What version of deluge?

Comment 4 Joost Ruis 2010-10-03 09:34:02 UTC

It was with previous RC.

Comment 5 Raúl Porcel (RETIRED) gentoo-dev

2010-12-18 12:22:19 UTC

Can you reproduce with 1.3.1?

Comment 6 Rafał Mużyło 2011-01-20 13:16:23 UTC

Due to comment 2, seems to be a dupe of bug 351897.