Bug#794765: Please provide debug build of pyside
On Wed, Aug 12, 2015 at 08:29:28PM +0200, Didier 'OdyX' Raboud wrote: Le mercredi, 12 août 2015, 16.00:22 Goswin von Brederlow a écrit : Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit : every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. Since 1.0.9-2, debug packages are not built anymore, as they were huge to build and resulted in insanely big binary packages, see http://snapshot.debian.org/package/pyside/1.0.9-1/ . The -dbg build got 1% tests passed, 405 tests failed out of 408. Lots of failures in refrence counts, tests/QtGui/qmainwindow_test.py and tests/QtWebKit/shouldInterruptjavascript_test.py hang and need to be manually killed, lots of segfaults in the tests and finally: Yes. This was the other problem with debug builds: there is something fishy going on with python-dbg builds and tests. Upstream is basically unresponsive and I'm reaching my limits (in terms of competences, as well as motivation). Frankly, I'm only a PySide maintainer because I was initially interested in it in the context of debian-mobile, but I'm not at all using PySide (although I like the idea of doing Qt in python). So the status is not actively involved, but welcoming patches. I'm happy to hand maintainership over too, only staying because I feel responsible (although less and less). When was the last time you did a debug build? For 1.0.9-2, apparently. PS: That's why I want debug packages from the start no matter how big they are. If they aren't autobuild then by the time you need them they don't work. I welcome patches though??? :) I know it's an easy answer, but that's the best one I can offer. Cheers, OdyX If I get a spare hour somewhere I can send patches for the control file and .install file fixes easy enough. The test suite failures get ignored so that isn't a stopper. I tested the resulting debs with python3-dbg and they work fine. So it's something fishy in the test suite itself as you suggest. I would suggest not running them for -dbg package because like you I don't care enough to fix something that complicated and fishy. I would suggest not running them for -dbg package because like you I don't care enough to fix something that complicated and fishy. The blocking tests are the main problem. I don't know why but I see that in basically every single test suite out there. None of them seem to come with a default timeout out of the box so any hanging test will hang forever. And usualy the test suite frameworks are hugely complex that adding that feature is not trivial. I'm not sure if I will find the time and motivation to delve that deep into it any time soon. I didn't check the build log closely but since PySide autobuilds without debug it seems likely that the test cases only hang for debug packages. So disabling the test suite for them might be a quick fix for that problem too. That's probably easy enough to try. MfG Goswin
Bug#794765: Please provide debug build of pyside
On Thu, Aug 06, 2015 at 05:51:59PM +0200, Didier 'OdyX' Raboud wrote: Control: found -1 1.0.9-2 Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit : every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. Since 1.0.9-2, debug packages are not built anymore, as they were huge to build and resulted in insanely big binary packages, see http://snapshot.debian.org/package/pyside/1.0.9-1/ . You can still build these yourself, see: http://sources.debian.net/src/pyside/1.2.2-1/debian/README.source Is this enough for you? I really don't want to add the debug packages back (and don't plan much PySide work at all, btw). Cheers, OdyX Pyside should at least the standard -dbg packages with the striped symbols so gdb backtraces make sense. It would be nice to have everything for python3-dbg because it's a pain to build debug packages when you need them. Esspecially when more packages start not shiping them. But if the size is preventing that for PySide then there isn't much to do there. Problem is that recompiling pyside might not show the bug anymore since the toolchain and build dependencies will have changed. Makes it real hard to debug memory/stack corruption bugs. Last building debug packages according to README.source does not work: dpkg-source: error: syntax error in pyside-1.2.1/debian/control at line 383: duplicate field Package found There is an empty line missing before Package: python-pyside-dbg. Either debian/control.in needs to end in an empty line or debian/control.dbg-packages needs to start with one. MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794765: Please provide debug build of pyside
On Thu, Aug 06, 2015 at 05:51:59PM +0200, Didier 'OdyX' Raboud wrote: Control: found -1 1.0.9-2 Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit : every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. Since 1.0.9-2, debug packages are not built anymore, as they were huge to build and resulted in insanely big binary packages, see http://snapshot.debian.org/package/pyside/1.0.9-1/ . You can still build these yourself, see: http://sources.debian.net/src/pyside/1.2.2-1/debian/README.source Is this enough for you? I really don't want to add the debug packages back (and don't plan much PySide work at all, btw). Cheers, OdyX Some hours of building later: The -dbg build got 1% tests passed, 405 tests failed out of 408. Lots of failures in refrence counts, tests/QtGui/qmainwindow_test.py and tests/QtWebKit/shouldInterruptjavascript_test.py hang and need to be manually killed, lots of segfaults in the tests and finally: # Do the legacy install for the rest dh_install -ppython-pyside-dbg --sourcedir=debian/tmp-dbg dh_install -ppython3-pyside-dbg --sourcedir=debian/tmp-dbg dh_install: python3-pyside-dbg missing files (usr/lib/*/cmake/PySide-*/*dmu.cmake), aborting make[1]: *** [override_dh_install_2] Error 255 make[1]: Leaving directory `/build/brederlo/pyside/pyside-1.2.1' make: *** [binary] Error 2 When was the last time you did a debug build? MfG Goswin PS: That's why I want debug packages from the start no matter how big they are. If they aren't autobuild then by the time you need them they don't work.
Bug#794765: Please provide debug build of pyside
Le mercredi, 12 août 2015, 16.00:22 Goswin von Brederlow a écrit : Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit : every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. Since 1.0.9-2, debug packages are not built anymore, as they were huge to build and resulted in insanely big binary packages, see http://snapshot.debian.org/package/pyside/1.0.9-1/ . The -dbg build got 1% tests passed, 405 tests failed out of 408. Lots of failures in refrence counts, tests/QtGui/qmainwindow_test.py and tests/QtWebKit/shouldInterruptjavascript_test.py hang and need to be manually killed, lots of segfaults in the tests and finally: Yes. This was the other problem with debug builds: there is something fishy going on with python-dbg builds and tests. Upstream is basically unresponsive and I'm reaching my limits (in terms of competences, as well as motivation). Frankly, I'm only a PySide maintainer because I was initially interested in it in the context of debian-mobile, but I'm not at all using PySide (although I like the idea of doing Qt in python). So the status is not actively involved, but welcoming patches. I'm happy to hand maintainership over too, only staying because I feel responsible (although less and less). When was the last time you did a debug build? For 1.0.9-2, apparently. PS: That's why I want debug packages from the start no matter how big they are. If they aren't autobuild then by the time you need them they don't work. I welcome patches though… :) I know it's an easy answer, but that's the best one I can offer. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#794765: Please provide debug build of pyside
Source: pyside Severity: important Hi, every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. MfG Goswin -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794765: Please provide debug build of pyside
Control: found -1 1.0.9-2 Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit : every now and then pyside crashes with a segfault. Most often because it doesn't play nice with the python GC and widgets have to keep python objects stored in C++ alive manually. But sometimes it isn't obvious where and why pyside segfaults. For those it would be nice if one could use python3-dbg and get better gdb backtraces for the application. But this requires a debug build of pyside. Please provide a debug build of pyside. Since 1.0.9-2, debug packages are not built anymore, as they were huge to build and resulted in insanely big binary packages, see http://snapshot.debian.org/package/pyside/1.0.9-1/ . You can still build these yourself, see: http://sources.debian.net/src/pyside/1.2.2-1/debian/README.source Is this enough for you? I really don't want to add the debug packages back (and don't plan much PySide work at all, btw). Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
