[kdevelop] [Bug 385398] kdevelop : crash after hitting enter in code editor

2017-10-05 Thread RJVB 
https://bugs.kde.org/show_bug.cgi?id=385398

--- Comment #3 from RJVB  ---
OK, now I'm curious. The stack backtrace in 384404 doesn't look like the one I
get at all, at least not the part in QtQML. How can you know it's the same bug?

It'd be extremely nice if there were a workaround/fix for this, applicable
either to KTextEditor or to Qt < 5.9 . 5.9 drops support for older OS versions
on Mac.

FWIW, this is what I get on Linux:

Program received signal SIGSEGV, Segmentation fault.
0x7fffce25dd77 in ?? ()
(gdb) bt
#0  0x7fffce25dd77 in ?? ()
#1  0x00fc6a40 in ?? ()
#2  0x00032000 in ?? ()
#3  0x7fffbd54f540 in ?? ()
#4  0x00fc6a40 in ?? ()
#5  0x00fc6a40 in ?? ()
#6  0x7244d108 in getValue (attrs=..., v=..., this=0xfc6a40)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/jsruntime/qv4object_p.h:230
#7  QV4::Object::internalGet (this=0xfc6a40, name=0x7fffbd54f548,
hasProperty=0x7fffbd54f418)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/jsruntime/qv4object.cpp:629
#8  0x72419553 in get (hasProperty=0x72863d60
, name=0x7fffbd54f4a0, 
this=)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/include/QtQml/5.8.0/QtQml/private/../../../../../src/qml/jsruntime/qv4object_p.h:326
#9  QV4::ExecutionContext::getPropertyAndBase (this=0x7fffbd54f418,
name=0x7fffbd54f4a0, base=0x0)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/jsruntime/qv4context.cpp:509
#10 0x724a4273 in call (d=0x7fffbd54f458, scope=..., this=)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/jsruntime/qv4object_p.h:352
#11 QV4::Runtime::method_callActivationProperty (engine=,
nameIndex=, 
callData=0x7fffbd54f458)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/jsruntime/qv4runtime.cpp:982
#12 0x7fffce2a1956 in ?? ()
#13 0x0001 in ?? ()
#14 0x in ?? ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385398] kdevelop : crash after hitting enter in code editor

2017-10-05 Thread Kevin Funk 
https://bugs.kde.org/show_bug.cgi?id=385398

Kevin Funk  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Kevin Funk  ---


*** This bug has been marked as a duplicate of bug 384404 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385398] kdevelop : crash after hitting enter in code editor

2017-10-05 Thread RJVB 
https://bugs.kde.org/show_bug.cgi?id=385398

--- Comment #1 from RJVB  ---
Turns out this is reproducible:
- Use the proposed "recover data" feature after reopening the session and
parsing stopped.
- hit enter after the new line

The line in question, in DocumentationController::documentationProviders():

qWarning() << Q_FUNC_INFO << "Current documentation providers:" << ret;

inserted before the return statement, with an empty line above and below the
qWarning line.

The crash disappears after reverting to KTextEditor 5.35.0 .

-- 
You are receiving this mail because:
You are watching all bug changes.