kdev-python breakage in KF5
Radek Novacek
rnovacek at redhat.com
Tue Jan 20 08:18:25 UTC 2015
On Monday, January 19, 2015 04:53:38 PM Kevin Funk wrote:
> Heya,
>
> The following commit [1] introduced using DAIM in kdev-python.
>
> However, now, whenever kdev-python kicks in for me, this crashes KDevelop,
> because of the following assert:
>
> [kdevelop(6240)/(default) Python::AstBuilder::parse: ====> AST ====>
> building abstract syntax tree for
> "/home/kfunk/devel/src/kf5/extragear/kdevelop/kdevelop/debuggers/gdb/printer
> s/kde4.py" [kdevelop(6240)/(kdev.python.parser) Python::AstBuilder::parse:
> Got syntax tree from python parser: 1 1
> [kdevelop(6240)/(kdev.python.parser) Python::ParseSession::parse:
> Sucessfully parsed
> [kdevelop(6240)/(kdev.python.duchain)
> Python::DeclarationBuilder::DeclarationBuilder: Building Declarations
> [kdevelop(6240)/(default) qt_assert: ASSERT: "QThread::currentThread() ==
> qApp->thread()" in file
> /home/kfunk/devel/src/kf5/extragear/kdevelop/kdevelop/languages/plugins/cust
> om- definesandincludes/definesandincludesmanager.cpp, line 132
>
> Can someone fix this?
>
> [1]
> commit 30841ced2e416523b8a10f9deccb4dcc54561e38
> Author: Radek Novacek <rnovacek at redhat.com>
> Date: Mon Dec 15 09:13:50 2014 +0100
>
> Search for modules in custom include paths
I believe that this should fix it:
https://git.reviewboard.kde.org/r/122164/
I'm not quite sure that this approach is correct, suggestions welcomed.
Radek Novacek
More information about the KDevelop-devel
mailing list