On Tue, Sep 6, 2016 at 10:01 PM, Chris George <[email protected]> wrote:
> Segmentation faults are not very frequent, at least when I search this > forum. > > I receive one in the terminal window whenever I load Leo with python 3.5.2 > and PyQt 5.7.0 and the python_terminal plugin. I isolated it by disabling > all other plugins and then enabling it. > Sorry you are having trouble. There are several sources of segfaults. 1. Installation problems. 2 . Passing the wrong kind of pointer to Qt widgets. 3. Rare, but possible: actual bugs in Qt or OS code. As an example of 3, there was, iirc, a Linux bug that caused the scroll wheel to hard crash Leo. There have been several reports of problems with later Qt releases. In the past, Qt has seen fit to change their API's between releases so that old code breaks. The leoQt module is intended to paper over these differences so that the rest of Leo doesn't have to worry about such things. Not all plugins use the leoQt module, so this is not a perfect solution. In particular, changes to the Qt API could cause Leo to pass the wrong kind of pointer to Qt, and that could cause a segfault. Testing Leo on all recent versions of Qt has top priority. The traceback you give is better than most core dumps. It may be useful in tracking down the problem. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
