[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] =?utf-8?q?Debugging_segfault_in_PyQt_application=3F?=
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2013-12-20 22:36:55
Message-ID: f3125c29f47de18ad7d351a1a7a0fd10 () www ! riverbankcomputing ! com
[Download RAW message or body]

On 20-12-2013 9:02 pm, Jason Tiller wrote:
> Hi, all,
>
> I collaborate on a complex PyQt application.  We're experiencing
> segfaults that arise from QtCore, but I'm stumped as to how to drill
> down into the coredump and get useful information from the backtrace.
> Anybody have any suggestions as to a useful approach for debugging
> segfaults in PyQt applications?  We can currently cause the issue
> (fairly) reliably every 20 minutes or so with manual button mashing.

The backtrace itself is useful so long as it contains debugging 
symbols.

Phil
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]