[cairo-bugs] [Bug 92567] New: Difficult to build debug version of pycairo

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Oct 21 06:26:55 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=92567

            Bug ID: 92567
           Summary: Difficult to build debug version of pycairo
           Product: cairo
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: chris at chris-wilson.co.uk
          Reporter: alexandru.balut at gmail.com
        QA Contact: cairo-bugs at cairographics.org

Created attachment 119029
  --> https://bugs.freedesktop.org/attachment.cgi?id=119029&action=edit
Attempt at creating a python3-cairo-dbg package in Debian

When developing a Gtk app in Python, it's useful to be able to debug segfaults
taking place in the C backend. The Python backtrace provided by gdb is pretty
useless unless the debug packages are installed, for example:
https://packages.debian.org/search?keywords=python3-dbg Without the debug
packages, useful info like the method names are "optimized out" and are not
displayed.

In Debian, debugging Gtk apps with python3-dbg does not seem to be possible
because there is no debug version of python3-cairo. For example, there is a
debug version of python-cairo called python-cairo-dbg, but there is no
python3-cairo-dbg for python3-cairo.

I poked about this in oftc.net #debian-python and I was told:
<p1otr> add binary package in debian/control, add python3-all-dbg to
Build-Depends and if you use pybuild, that's all
<p1otr> my first try was: 315465 but then I realized it's waf so I give up,
life is too short for waf
<p1otr> (if you want to continue: the problem is with waf using some options
from dbg interpreter and some from regular one, f.e. it calls pythnon3.5-config
instead of python3.5-dbg-config)

See the attachment for the attempt at creating python3-cairo-dbg.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cairographics.org/archives/cairo-bugs/attachments/20151021/987edce6/attachment.html>


More information about the cairo-bugs mailing list