Pycharm debugger instantly exits with code 139

Question

After upgrading from Pycharm 2017.2.3to Pycharm 2017.1.4Pycharm, Debugger suggested building cpython (or the associated sth):

path/to/my/python/opt/pycharm-community-2017.1.4/helpers/pydev/setup_cython.py build_ext --inplace

After I have done this, the debugger instantly returns this error:

Process terminated with exit code 139 (interrupted by signal 11: SIGSEGV)

I found that there was a similar problem with cpython ( https://youtrack.jetbrains.com/issue/PY-23273 ), but I can’t use the workaround mentioned there because I don’t have enough files that it suggests deleting .. I'm not using Cython, I would like to ignore this post about creating it ..

I am on Linux ( SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux)

Python 2.7

Answer 1

I fixed this by disabling the option PyQt compatiblein the PyCharms debugger settings (build, execution, deployment> Python debugger). I do not use PyQt, so I have not encountered any problems

Answer 2

I changed Pycharm from 2017.1.4to Pycharm EAP 2017.2, but without effect.

I solved the problem by creating a new python virtual environment and changing the default Pycharm interpreter. Not the fastest solution, I think, but at least it worked.

Pycharm now offers suggestions for creating something for Cython, but now I just ignore it.

Answer 3

.

, PYQT. pyqt Pycharm "Preference- > Project: - > Project Interpreter" pyqt "-", .

, script, " PyQt4 import QtGui". pyqt . . pyqt, debug !

, , - , , . pyqt, matplotlib - .

Answer 4

, , pyqt, , ....

• pyqt matplotlib
• pyqt
• matplotlib

.

Answer 5

, pyqt5.

sudo apt-get remove python3-pyqt5

This did not happen to me due to the creation of cpython. This was because I installed an unrelated program. Hope this helps.

Answer 6

I had the same thing with 2017.1.4 The problem was resolved after upgrading to 2017.1.5

Answer 7

Try to clear all your breakpoints. Worked for me. Also check that you have no problem running Run instead of Debug.