Pycharm 调试器立即退出 139 代码 [英] Pycharm debugger instantly exits with 139 code

查看:46
本文介绍了Pycharm 调试器立即退出 139 代码的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Pycharm 2017.2.3 升级到 Pycharm 2017.1.4 Pycharm 的 Debugger 建议构建 cpython(或与之相关的):

After upgrade from Pycharm 2017.2.3 to Pycharm 2017.1.4 Pycharm's Debugger suggested to build cpython (or sth associated with it):

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

在我这样做之后,Debugger 现在立即返回此错误:

After I did this, Debugger now instantly returns this error:

进程以退出代码 139 结束(被信号 11:SIGSEGV 中断)

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

我发现 cpython 也存在类似问题 (https://youtrack.jetbrains.com/issue/PY-23273)但我不能使用那里提到的解决方法,因为我错过了它建议删除的文件......我没有使用 cython,我希望我忽略这条关于构建它的消息..

I found out that there was similar issue with cpython (https://youtrack.jetbrains.com/issue/PY-23273) but I cannot use the workaround mentioned there because I am missing the files it suggest to remove... I am not using cython, I wish I ignored this message about building it..

我在 linux 上(SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux)

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

Python 2.7

推荐答案

我已经通过在 PyCharms 的调试器设置(构建、执行、部署 > Python 调试器)中禁用 PyQt compatible 选项来修复它.我没有使用PyQt,所以我没有遇到任何麻烦

I've fixed it by disabling PyQt compatible option in PyCharms's debugger settings (Build, Execution, Deployment > Python Debugger). I don't use PyQt, so I have not met any troubles

这篇关于Pycharm 调试器立即退出 139 代码的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆