[kdevelop] [Bug 368460] function signature picks up template parameter names
https://bugs.kde.org/show_bug.cgi?id=368460 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #3 from Francis Herne --- This gets much weirder with multiple parameters. The last parameter disappears entirely, and the types are offset from the parameter names. Compare the tooltip to the actual definition here: http://www.flherne.uk/files/Screenshot_20160912_102316.png When there are multiple versions with different parameter lists, it gets even more confusing because the parser connects uses to the wrong definition. The three variants of DeclarationBuilder::visitVariableDeclaration() in kdev-python/duchain/declarationbuilder.cpp display this quite well/badly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367803] Crash when viewing file.
https://bugs.kde.org/show_bug.cgi?id=367803 Francis Herne changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Francis Herne --- My fault, didn't properly delete some files when upgrading. Thanks to olijg on IRC. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367803] New: Crash when viewing file.
https://bugs.kde.org/show_bug.cgi?id=367803
Bug ID: 367803
Summary: Crash when viewing file.
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: m...@flherne.uk
Just compiled git master of KDevelop/kdevplatform/kdev-python, having been
using the 5.0 branch up to now. KDevelop crashes when opening/viewing any file,
regardless of the content.
kdevelop --ps works fine. Selecting any of my existing sessions, all of which
have open files, triggers a crash. Creating a new session does not crash,
giving a working KDevelop window, until I open or create a file.
Reproducible: Always
Steps to Reproduce:
1. Start kdevelop.
2. Open or create a file.
Backtrace is somewhat variable, but always seems to finish inside addPlugin().
CLI output and backtrace below:
(gdb) run
Starting program: /usr/bin/kdevelop
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffd60ba700 (LWP 17522)]
[New Thread 0x7fffc700 (LWP 17523)]
org.kde.knotifications: Audio notification requested, but sound file from
notifyrc file was not found, aborting audio notification
[New Thread 0x7fffc18c1700 (LWP 17524)]
cannot find .rc file "kdevlldbui.rc" for component "kdevlldb"
[New Thread 0x7fffb1ae3700 (LWP 17525)]
Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
0x7559306a in KActionCollection::addAssociatedWidget(QWidget*) () from
/usr/lib/libKF5XmlGui.so.5
(gdb) bt full
#0 0x7559306a in KActionCollection::addAssociatedWidget(QWidget*) ()
from /usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#1 0x755ebc4e in KXMLGUIClient::beginXMLPlug(QWidget*) () from
/usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#2 0x755f7d43 in KXMLGUIFactory::addClient(KXMLGUIClient*) () from
/usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#3 0x77a2d228 in KDevelop::MainWindowPrivate::addPlugin
(this=0x87ee70, plugin=0x277afd0) at
/home/flh/projects/kdevplatform/shell/mainwindow_p.cpp:97
__PRETTY_FUNCTION__ = "void
KDevelop::MainWindowPrivate::addPlugin(KDevelop::IPlugin*)"
ownClient = 0x2768d68
#4 0x77a2cb8f in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KDevelop::MainWindowPrivate::*)(KDevelop::IPlugin*)>::call (f=
(void (KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x77a2d022
, o=0x87ee70,
arg=0x7fffa4f0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:507
No locals.
#5 0x77a2c610 in QtPrivate::FunctionPointer::call,
void> (f=
(void (KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x77a2d022
, o=0x87ee70,
arg=0x7fffa4f0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:526
No locals.
#6 0x77a2baaf in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x8e9de0,
r=0x87ee70, a=0x7fffa4f0, ret=0x0)
at /usr/include/qt/QtCore/qobject_impl.h:149
No locals.
#7 0x710ea85e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#8 0x761c299f in KDevelop::IPluginController::pluginLoaded
(this=0x8e7db0, _t1=0x277afd0) at
/home/flh/projects/kdevplatform/build/interfaces/moc_iplugincontroller.cpp:235
_a = {0x0, 0x7fffa4e0}
#9 0x77a38604 in KDevelop::PluginController::loadPluginInternal
(this=0x8e7db0, pluginId=...) at
/home/flh/projects/kdevplatform/shell/plugincontroller.cpp:565
timer = {t1 = 147598, t2 = 299522362}
info = {m_metaData = {d = 0x9addf0, o = 0xa8b218}, m_fileName = {static
null = {}, d = 0x9a5a30}, d = {d = 0x0}}
__PRETTY_FUNCTION__ = "KDevelop::IPlugin*
KDevelop::PluginController::loadPluginInternal(const QString&)"
missingInterfaces = {> = {>
= {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x7116c180 }, d =
0x7116c180 }}, }
failedDependency = {static null = {}, d =
0x7116a360 }
loader =
factory = 0x89c3f0
plugin = 0x277afd0
group =
#10 0x77a3908a in KDevelop::PluginControlleroperator()(const KPluginMetaData &) const
(__closure=0x7fffaa30, info=...)
at /home/flh/projects/kdevplatform/shell/plugincontroller.cpp:645
plugin = 0x0
plugins = @0x7fffaba0: {> =
{}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x7116c180 }, d =
0x7116c180 }}
this = 0x8e
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 --- Comment #10 from Francis Herne --- Oh, and it doesn't have to be search, the usual colon-triggered command bar (and any others) are also affected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 --- Comment #9 from Francis Herne --- I was wrong above. EmulatedCommandBar::eventFilter() _is_ called, catches m_suspendEditEventFiltering and returns false to reject the event. Because the event was rejected it's propagated to KateViewInternal::eventFIlter(), which then causes the infinite loop. Despite the comment in EmulatedCommandBar::handleKeyPress() I'm still confused as to what the event duplication tries to achieve or why it's sent to a child widget. If the LineEdit accepts it we wouldn't have received the original, so it's guaranteed to loop? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 --- Comment #8 from Francis Herne --- Backtrace: #0 0x7fffdb2d20b8 in ?? () from /usr/lib/qt/plugins/styles/breeze.so #1 0x7490d8b6 in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #2 0x755ede78 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #3 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #4 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress (this=0xfa8c40, keyEvent=0x7f7ff6e0) at /home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310 #5 0x77902574 in KateVi::InputModeManager::handleKeypress (this=0x9e5160, e=0x7f7ff6e0) at /home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147 #6 0x778c199d in KateViInputMode::keyPress (this=0x93d460, e=0x7f7ff6e0) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292 #7 0x778c125f in KateViInputMode::stealKey (this=0x93d460, k=0x7f7ff6e0) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144 #8 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80, obj=0x9ee140, e=0x7f7ff6e0) at /home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280 #9 0x7490d9e1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #11 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress (this=0xfa8c40, keyEvent=0x7f7ffb00) at /home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310 #13 0x77902574 in KateVi::InputModeManager::handleKeypress (this=0x9e5160, e=0x7f7ffb00) at /home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147 #14 0x778c199d in KateViInputMode::keyPress (this=0x93d460, e=0x7f7ffb00) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292 #15 0x778c125f in KateViInputMode::stealKey (this=0x93d460, k=0x7f7ffb00) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144 #16 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80, obj=0x9ee140, e=0x7f7ffb00) at /home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280 #17 0x7490d9e1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #20 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress (this=0xfa8c40, keyEvent=0x7f7fff20) at /home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310 #21 0x77902574 in KateVi::InputModeManager::handleKeypress (this=0x9e5160, e=0x7f7fff20) at /home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147 #22 0x778c199d in KateViInputMode::keyPress (this=0x93d460, e=0x7f7fff20) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292 #23 0x778c125f in KateViInputMode::stealKey (this=0x93d460, k=0x7f7fff20) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144 #24 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80, obj=0x9ee140, e=0x7f7fff20) at /home/flh/projects/ktexteditor/src/view/kateviewinternal.cpp:2280 #25 0x7490d9e1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #26 0x755ede15 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x755f6f86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x77918857 in KateVi::EmulatedCommandBar::handleKeyPress (this=0xfa8c40, keyEvent=0x7f800340) at /home/flh/projects/ktexteditor/src/vimode/emulatedcommandbar/emulatedcommandbar.cpp:310 #29 0x77902574 in KateVi::InputModeManager::handleKeypress (this=0x9e5160, e=0x7f800340) at /home/flh/projects/ktexteditor/src/vimode/inputmodemanager.cpp:147 #30 0x778c199d in KateViInputMode::keyPress (this=0x93d460, e=0x7f800340) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:292 #31 0x778c125f in KateViInputMode::stealKey (this=0x93d460, k=0x7f800340) at /home/flh/projects/ktexteditor/src/inputmode/kateviinputmode.cpp:144 #32 0x7782aa6b in KateViewInternal::eventFilter (this=0x9fdf80, obj=0x9ee140, e=0x7f800340) at /home/flh/projects/ktexteditor/src/view/ka
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #7 from Francis Herne --- Assuming I'm looking at the same bug... For me it happens frequently when using '/', with a variety of keys and my usual UK keyboard layout. Reverting https://quickgit.kde.org/?p=ktexteditor.git&a=commit&h=025edb11ca9b0fa3685802e6c9cb608a4daa7911 avoids it. I get a loopy backtrace several tens of thousands of calls deep until the stack fills up - line 310 of emulatedcommandbar.cpp re-emits a key event, which is then handled again resulting in an endless cycle of duplicate events. The surrounding 'm_suspendEditEventFiltering' assignments seem intended to avoid these, but the only method checking that attribute is EmulatedCommandBar::eventFilter() which isn't called. KateViewInternal::eventFilter() *is* called, so the patch author might have been confused about which class object would handle the duplicated event. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365248] Krunner crash when typing first letter or clicking setting button
https://bugs.kde.org/show_bug.cgi?id=365248 --- Comment #12 from Francis Herne --- Package 0.9.8-2 of libqalculate fixed it. https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/libqalculate&id=33746670cde03a9ca3078db93f0c5229845b3803 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365248] Krunner crash when typing first letter or clicking setting button
https://bugs.kde.org/show_bug.cgi?id=365248 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #10 from Francis Herne --- This is reportedly fixed upstream: https://github.com/Qalculate/libqalculate/issues/4 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 359912] Type not recognized in expressions with multiple subscripts
https://bugs.kde.org/show_bug.cgi?id=359912 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #1 from Francis Herne --- This is broken when subscripting most expressions that aren't simply names, in cases where the returned type is found by looking at __getitem__(). Lists, tuples, dicts and some other builtin types are handled separately. Another example: class SomeClass: def __getitem__(self, key): return "Test" def some_func(): return SomeClass() aaa = some_func()[3] # should be str, but is mixed. I'll try to fix it, if I can find how all this Declaration stuff works. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364056] Kdevelop crashed when modifying custom include path
https://bugs.kde.org/show_bug.cgi?id=364056 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #1 from Francis Herne --- This looks very much like https://bugs.kde.org/show_bug.cgi?id=364433, which is now fixed. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 360070] Splash screen glitch with external monitor
https://bugs.kde.org/show_bug.cgi?id=360070 --- Comment #4 from Francis Herne --- ^ above output is from .xinitrc: `xrandr > xrandr.out; exec startkde` Behaviour changed apparently randomly while I was testing things...fun to debug, I'm sure. Initially, the incorrect splash screen lasted for the entire period, and disappeared suddenly when the correct ones finished fading out. After accidentally unplugging (and reconnecting) the monitor, it again started to correct itself partway through. At one point, incorrect output appeared on *both* displays - in addition to the small splash overlaid on the large display, elements of the larger splash (K logo, progress bar) were mirrored on the small one. This happened twice consecutively, and then didn't happen again. On a couple of occasions (out of a dozen or so tries), the splash screen appeared normally. Sometimes the logout fade wasn't affected. Once, an 800x600 version of the logout-options bar appeared centered on the laptop display (rather than in the top-left like the other artefacts). Otherwise it always appeared on the external monitor despite that not being the primary display. Sorry, I just can't spot the patterns in this behaviour, so I'm just dropping it on you for now in case it's useful. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 360070] Splash screen glitch with external monitor
https://bugs.kde.org/show_bug.cgi?id=360070 --- Comment #3 from Francis Herne --- Similar behaviour with Plasma/KWin 5.7.0, Qt 5.7.0, KF 5.23.0. KScreen is used, I have no static configuration. I only have an 800x600 VGA monitor handy, so the appearance is slightly different now. Output on the external monitor is still correct, output on the 1600x900 laptop display appears correct except that a copy of the 800x600 output is overlaid in the upper left corner. When the compositor is enabled, a similar effect appears with the logout fade - an 800x600 region, at the upper left of the laptop display, is much darker than the rest of the screen, presumably because a second grey region is overlaid there. (with the compositor disabled, there is no logout fade). Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767 LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 310mm x 170mm 1600x900 60.01*+ 40.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 800x450 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 --- Comment #1 from Francis Herne --- With today's 5.0-git, occurs about one time in three. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] New: Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 Bug ID: 364433 Summary: Crash when using Solve -> Add custom include path Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: m...@flherne.uk When including a file that KDevelop's parser hasn't found, right-clicking on the include shows a dialog with "Solve: 'filename' not found". This has a single menu option, "Add custom include path", which opens the project configuration dialog. When *closing* this dialog, with either "Ok" or "Cancel", KDevelop segfaults. This doesn't happen when accessing it via the little Alt-N solution bar, or via the menus. #0 0x7108091e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #1 0x761b6735 in KDevelop::IAssistantAction::executed (this=0x2cf3a00, _t1=0x2cf3a00) at /home/flh/projects/kdevplatform/build/interfaces/moc_iassistant.cpp:149 #2 0x7fffb456ff00 in AddCustomIncludePathAction::execute (this=0x2cf3a00) at /home/flh/projects/kdevelop/languages/clang/duchain/missingincludepathproblem.cpp:56 #3 0x761a7d6e in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KDevelop::IAssistantAction::*)()>::call(void (KDevelop::IAssistantAction::*)(), KDevelop::IAssistantAction*, void**) ( f=&virtual table offset 128, o=0x2cf3a00, arg=0x7fffa2a0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:501 #4 0x761a7d00 in QtPrivate::FunctionPointer::call, void>(void (KDevelop::IAssistantAction::*)(), KDevelop::IAssistantAction*, void**) ( f=&virtual table offset 128, o=0x2cf3a00, arg=0x7fffa2a0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:520 #5 0x761a79bb in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x2ce7690, r=0x2cf3a00, a=0x7fffa2a0, ret=0x0) at /usr/include/qt/QtCore/qobject_impl.h:143 #6 0x710812cc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #7 0x71d77b32 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #8 0x71d7a740 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #9 0x71f0502a in ?? () from /usr/lib/libQt5Widgets.so.5 #10 0x71f0b1bc in ?? () from /usr/lib/libQt5Widgets.so.5 #11 0x71f0f336 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x71dc6b38 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x71f0fdeb in QMenu::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x71d8106c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x71d873b7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x71053e70 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x71d85a85 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/libQt5Widgets.so.5 #18 0x71de19c0 in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x71de3ca3 in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x71d8106c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x71d864ff in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x71053e70 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #23 0x715a0113 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #24 0x715a1925 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #25 0x7157f5fb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #26 0x7fffd75c74d0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #27 0x7fffe612edd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x7fffe612f040 in ?? () from /usr/lib/libglib-2.0.so.0 #29 0x7fffe612f0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0x710aa2cf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #31 0x7105202a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #32 0x71f09ffd in QMenu::exec(QPoint const&, QAction*) () from /usr/lib/libQt5Widgets.so.5 #33 0x71f1a915 in ?? () from /usr/lib/libQt5Widgets.so.5 #34 0x71081229 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #
[frameworks-ktexteditor] [Bug 360418] Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418 Francis Herne changed: What|Removed |Added Version|5.19.0 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 360418] Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418 --- Comment #3 from Francis Herne --- This is caused by the command 'g' not actually existing; KTE crashes when given a range for a nonexistent command. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 362913] Crash when parsing file.
https://bugs.kde.org/show_bug.cgi?id=362913 --- Comment #6 from Francis Herne --- And yes, the fix works here. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 362913] Crash when parsing file.
https://bugs.kde.org/show_bug.cgi?id=362913 --- Comment #5 from Francis Herne --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 362913] Crash when parsing file.
https://bugs.kde.org/show_bug.cgi?id=362913 --- Comment #2 from Francis Herne --- That isn't quite true for me. That construct _doesn't_ seem to crash kdev-python if it's actually inside a function, or a class definition. It does crash if it's at module level, or inside a for-loop. Crashes: A = 1, 2, 3 return [x for x in A] Crashes: A = 1, 2, 3 for q in 4, 5: return [x for x in A] Doesn't crash: A = 1, 2, 3 def foo(): return [x for x in A] Doesn't crash: A = 1, 2, 3 class B: return [x for x in A] -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 362913] New: Crash when parsing file.
https://bugs.kde.org/show_bug.cgi?id=362913
Bug ID: 362913
Summary: Crash when parsing file.
Product: kdev-python
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: m...@svenbrauch.de
Reporter: francis.he...@yahoo.co.uk
CC: m...@svenbrauch.de
Arch Linux x86_64, 5.0 branches of kdev-python/kdevelop/kdevplatform as of
March 14 (still...).
When parsing the file contents below, kdev-python crashes.
Reproducible: Always
Steps to Reproduce:
Put the content below in a text file, open it in KDevelop.
Contents
from collections import namedtuple
Link = namedtuple('Link', ('origin', 'tag', 'target', 'inverse_tag'))
def __link_inverse(self):
"""View a link from the other end (should be classmethod)"""
return Link(self.target, self.inverse_tag, self.origin, self.tag)
Link.inverse = __link_inverse
class Network:
def __init__(self):
self.links = []
def __getitem__(self, key):
if not isinstance(key, tuple):
if isinstance(key, int):
return self.links[key]
key = (key,)
key += (...,) * (4 - len(key))
def match(link):
return all(query in (value, ...) for query, value in zip(key, link))
return [link for link in self.links if match(link)]
===
End contents
Actual Results:
KDevelop crashes:
- When editing the file into that state.
- When pressing 'recover changes' after the crash.
- When pasting the contents into a new file, outside the project tree, and
opening that.
KATE/KWrite don't crash.
Expected Results:
KDevelop doesn't crash.
Output/backtrace
Parsing Succeeded
> PARSING > parsing file
QUrl("file:///home/flh/projects/PIMesh/network3.py") ; has priority 0
> AST > building abstract syntax tree for
"/home/flh/projects/PIMesh/network3.py"
> DUCHAIN > rebuilding duchain for
"/home/flh/projects/PIMesh/network3.py" (was built before)
> DUCHAIN > rebuilding duchain for
"/home/flh/projects/PIMesh/network3.py" (was built before)
ASSERT: "currentContext()" in file
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/duchain/contextbuilder.cpp,
line 257
Thread 14 "Queue(0x2a36a60" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff9bfff700 (LWP 18604)]
0x7439c295 in raise () from /usr/lib/libc.so.6
(gdb) bt full
#0 0x7439c295 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x7439d6da in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x74b23c61 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#3 0x74b1eebe in qt_assert(char const*, char const*, int) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#4 0x7fffa2df0e32 in Python::ContextBuilder::visitComprehensionCommon
(this=0x7fff9bffead0, node=0x7fff90123fe0) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/duchain/contextbuilder.cpp:257
lock = {m_lock = 0x72aebba0 , m_locked =
true, m_timeout = 0}
range = {start = {line = 23, column = 7}, end = {line = 23, column =
50}}
#5 0x7fffa735441a in Python::AstDefaultVisitor::visitCode
(this=this@entry=0x7fff9bffeb28, node=node@entry=0x7fff90346020) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/parser/astdefaultvisitor.cpp:79
statement =
_container_ = {c = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x7fff902e3570}, d = 0x7fff902e3570}}, i = {i =
0x7fff902e35b8}, e = {i = 0x7fff902e35c0}, control = 1}
#6 0x7fffa2df143a in Python::ContextBuilder::visitCode
(this=0x7fff9bffead0, node=0x7fff90346020) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/duchain/contextbuilder.cpp:319
doc_url = {static null = {}, d = 0x9d9080}
doc = {m_index = 123018}
#7 0x7fffa328ec59 in KDevelop::AbstractContextBuilder::supportBuild (this=0x7fff9bffead0, node=0x7fff90346020,
context=)
at
/usr/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:134
No locals.
#8 0x7fffa328de6c in KDevelop::AbstractUseBuilder::buildUses (node=0x7fff90346020,
this=0x7fff9bffead0)
at
/usr/include/kdevplatform/language/duchain/builders/abstractusebuilder.h:72
top =
#9 Python::ParseJob::run (this=) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/pythonparsejob.cpp:178
builder =
{> = { =
{> = { =
{> =
{_vptr.AbstractContextBuilder = 0x7fffa3035730 , m_identifier = {m_index = 65538, {
dd = 0x732e86d0
, cd = 0x732e86d0
}}, m_url
[kfile] [Bug 185433] Filenames containing double quotes cannot be opened with KFileDialog
https://bugs.kde.org/show_bug.cgi?id=185433
Francis Herne changed:
What|Removed |Added
CC||francis.he...@yahoo.co.uk
--- Comment #9 from Francis Herne ---
This is more serious than it says on the tin.
It affects _saving_ files too...save to FooDoc("quotes").file, and pretty much
every KDE app will write to 'quotes'.
Best-case, the file isn't saved to where the user expected it but they notice.
Worse, it's saved somewhere else and they think they've lost all their work.
At least there's a popup before clobbering 'quotes' if it exists, but people
aren't good at paying attention to those.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 362613] Crash when opening files with double-quote(s) in name.
https://bugs.kde.org/show_bug.cgi?id=362613 --- Comment #2 from Francis Herne --- I suppose this is the right bug, unfixed for seven years: https://bugs.kde.org/show_bug.cgi?id=185433 Opening different files to the one requested seems seriously wrong to me. :-/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362613] Crash when opening files with double-quote(s) in name.
https://bugs.kde.org/show_bug.cgi?id=362613 --- Comment #1 from Francis Herne --- Correction: Steps to reproduce are true for a file with one doublequote, not two as shown. In case of two, opening a single file, KDevelop will open (create) a file with the fragment of the filename between the quotes. When opening multiple files, KDevelop may open/create files with the end fragments instead. Everything is wrong, anyway. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362613] New: Crash when opening files with double-quote(s) in name.
https://bugs.kde.org/show_bug.cgi?id=362613
Bug ID: 362613
Summary: Crash when opening files with double-quote(s) in name.
Product: kdevelop
Version: 4.90.91
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: file selector
Assignee: kdevelop-bugs-n...@kde.org
Reporter: francis.he...@yahoo.co.uk
When opening files containing one or more double-quote characters:
e.g. «Testfile("Word").txt» or «Test\"word.txt»
via the file selector, KDevelop crashes.
Opening such a file by itself via the file selector is impossible, when
clicking on the 'Open' button nothing happens. When ctrl-clicking or dragging
to select multiple files, one or more of which have a double-quote character in
their name, the result below occurs.
If doing this in a session, all future attempts to load that session will crash
KDevelop in the same way. The session must be deleted and recreated.
Opening such a file via the Filesystem pane, or from a CLI argument, is
successful.
KATE also fails to open such files, either reporting that parts of the filename
aren't files or opening the wrong file, but doesn't crash.
Gwenview and other KDE applications fail to open such files, but also don't
crash.
Hmm, this bug probably shouldn't be here. But I typed it now. :P
Reproducible: Always
Steps to Reproduce:
1. Create a file named 'Test-"File".txt'.
2. In the file selector, attempt to open that file.
- Clicking 'Open' will have no effect.
3. In the file selector, attempt to open that file along with at least one
other file.
- KDevelop will crash.
4. Restart KDevelop using the same session.
- KDevelop will crash again.
Actual Results:
ASSERT: "!inputUrl.fileName().isEmpty()" in file
/home/flh/projects/src/kdevplatform/shell/documentcontroller.cpp, line 226
On another occasion I got:
kdevplatform.language: INVALID URL ENCOUNTERED: "/home/flh/ "
QUrl("file:///home/flh/")
ASSERT: "isValidURL(url)" in file
/home/flh/projects/src/kdevplatform/language/backgroundparser/backgroundparser.cpp,
line 534
Backtrace:
=
Thread 1 "kdevelop" received signal SIGABRT, Aborted.
0x743ac2a8 in raise () from /usr/lib/libc.so.6
(gdb) bt full
#0 0x743ac2a8 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x743ad72a in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x74b2ef41 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#3 0x74b2a26e in qt_assert(char const*, char const*, int) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#4 0x722cee7e in KDevelop::BackgroundParser::addDocument
(this=, url=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
priority=priority@entry=0,
notifyWhenReady=notifyWhenReady@entry=0x0, flags=..., flags@entry=...) at
/home/flh/projects/src/kdevplatform/language/backgroundparser/backgroundparser.cpp:534
lock =
#5 0x722ef4a1 in KDevelop::DUChain::documentLoadedPrepare
(this=, doc=0x2433570) at
/home/flh/projects/src/kdevplatform/language/duchain/duchain.cpp:1534
url = {m_index = 495347}
lock = {m_lock = 0x72afbba0 , m_locked =
true, m_timeout = 0}
l = {val = 140737264991105}
standardContext = 0x0
chains = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x74dc9d40 }, d =
0x74dc9d40 }}
languages = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x74dc9d40 }, d =
0x74dc9d40 }}
__PRETTY_FUNCTION__ = "void
KDevelop::DUChain::documentLoadedPrepare(KDevelop::IDocument*)"
#6 0x74d46bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#7 0x76da0252 in KDevelop::IDocumentController::documentLoadedPrepare
(this=, _t1=_t1@entry=0x2433570) at
/home/flh/projects/src/build/interfaces/moc_idocumentcontroller.cpp:565
_a = {0x0, 0x7fffc3a8}
#8 0x76d93db0 in KDevelop::IDocument::notifyLoaded (this=0x2433570) at
/home/flh/projects/src/kdevplatform/interfaces/idocument.cpp:130
No locals.
#9 0x74d46bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#10 0x70a7c962 in
KTextEditor::Document::textChanged(KTextEditor::Document*) () from
/usr/lib/libKF5TextEditor.so.5
No symbol table info available.
#11 0x708e932b in KTextEditor::DocumentPrivate::openFile() () from
/usr/lib/libKF5TextEditor.so.5
No symbol ta
[kdev-python] [Bug 362515] Segfault in code completion
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #4 from Francis Herne ---
More backtrace:
Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa59be700 (LWP 13247)]
0x7fff88056020 in ?? ()
(gdb) bt full
#0 0x7fff88056020 in ?? ()
No symbol table info available.
#1 0x7fffa5a0081f in Python::ExpressionVisitor::ExpressionVisitor
(this=0x7fffa0040c60, ctx=) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/duchain/expressionvisitor.cpp:70
No locals.
#2 0x7fffa5c73969 in Python::visitorForString (str=...,
context=context@entry=0x7fff880b2240, scanUntil=..., scanUntil@entry=...)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:84
builder = {m_problems =
{ >> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }},
static pyInitLock = { = {d_ptr = {_q_value = {_M_b =
{_M_p = 0x0, }}
tmpAst = {value = 0x7fffa0051e50, d = 0x7fffa008e580}
v =
#3 0x7fffa5c77947 in
Python::PythonCodeCompletionContext::functionCallItems
(this=this@entry=0x7fffa0043080) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:144
resultingItems =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
functionCalled = 0x0
v = std::unique_ptr containing
0x74dc7ee0
lock = {m_lock = 0x74dc7ee0 , m_locked =
89, m_timeout = 32767}
__PRETTY_FUNCTION__ = "Python::PythonCodeCompletionContext::ItemList
Python::PythonCodeCompletionContext::functionCallItems()"
current = 0x74dc9d40
calltips = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x74dc9d40 }, d =
0x74dc9d40 }}
calltipItems =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
#4 0x7fffa5c7cb28 in Python::PythonCodeCompletionContext::completionItems
(this=0x7fffa0043080, abort=@0x42aa2d0: false, fullCompletion=)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:574
resultingItems =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
__PRETTY_FUNCTION__ = "virtual
QList >
Python::PythonCodeCompletionContext::completionItems(bool&, bool)"
#5 0x7fffa5c7c992 in Python::PythonCodeCompletionContext::completionItems
(this=this@entry=0x7fffa003bf20, abort=@0x42aa2d0: false,
fullCompletion=fullCompletion@entry=false)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:564
resultingItems =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
__PRETTY_FUNCTION__ = "virtual
QList >
Python::PythonCodeCompletionContext::completionItems(bool&, bool)"
#6 0x72408d24 in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x42aa2b0, context=..., position=..., followingText=...,
contextRange=..., contextText=...)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:167
items =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x2a21aa0}, d =
0x2a21aa0}}
tree =
{
>> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= {> = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc7ee0
}, d = 0x74dc7ee0 }}
__PRETTY_FUNCTION__ = "virtual void
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUContextPointer,
const KTextEditor::Cursor&, QString, const KTextEditor::Range&, const
QString&)"
completionContext = {d = 0x7fffa003bf20}
#7 0x72408772 in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x42aa2b0, context=..., position=..., view=0x4396780)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:129
[kdev-python] [Bug 362515] Segfault in code completion
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #1 from Francis Herne ---
Crashed again, backtrace looks a bit different:
Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa3477700 (LWP 13580)]
KDevelop::DUChainBase::rangeInCurrentRevision (this=0x0) at
/home/flh/projects/src/kdevplatform/language/duchain/duchainbase.cpp:157
157 DocumentChangeTracker* tracker =
ICore::self()->languageController()->backgroundParser()->trackerForUrl(url());
(gdb) bt full
#0 KDevelop::DUChainBase::rangeInCurrentRevision (this=0x0) at
/home/flh/projects/src/kdevplatform/language/duchain/duchainbase.cpp:157
tracker =
#1 0x7fffa373be72 in
Python::PythonCodeCompletionWorker::updateContextRange (this=,
contextRange=..., view=, context=...)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/worker.cpp:59
__PRETTY_FUNCTION__ = "virtual void
Python::PythonCodeCompletionWorker::updateContextRange(KTextEditor::Range&,
KTextEditor::View*, KDevelop::DUContextPointer) const"
#2 0x7240881f in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x45745e0, context=..., position=..., view=0x48111b0)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:108
lock = {val = 72823617}
lockDUChain = {m_lock = 0x72afbba0 , m_locked =
true, m_timeout = 0}
foreground = {m_locked = true}
doc = 0x4815ea0
__PRETTY_FUNCTION__ = "void
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUContextPointer,
const KTextEditor::Cursor&, KTextEditor::View*)"
range = {m_start = {m_line = 67, m_column = 0}, m_end = {m_line = 67,
m_column = 45}}
text = {static null = {}, d = 0x74dc7ee0
}
cursorPosition = {m_line = -223364192, m_column = 32767}
followingText =
#3 0x7240f232 in QtPrivate::FunctorCall, QtPrivate::List,
KTextEditor::Cursor const&, KTextEditor::View*>, void, void
(KDevelop::CodeCompletionWorker::*)(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*)>::call (arg=,
o=, f=)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:501
No locals.
#4 QtPrivate::FunctionPointer,
KTextEditor::Cursor const&,
KTextEditor::View*)>::call,
KTextEditor::Cursor const&, KTextEditor::View*>, void> (arg=,
o=, f=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:520
No locals.
#5 QtPrivate::QSlotObject,
KTextEditor::Cursor const&, KTextEditor::View*),
QtPrivate::List,
KTextEditor::Cursor const&, KTextEditor::View*>, void>::impl (which=, this_=, r=, a=,
ret=) at /usr/include/qt/QtCore/qobject_impl.h:143
No locals.
#6 0x74d47659 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#7 0x75a3e68c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
No symbol table info available.
#8 0x75a438f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
No symbol table info available.
#9 0x74d1a518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
No symbol table info available.
#10 0x74d1c3da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#11 0x74d6f883 in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#12 0x7fffec105f07 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
No symbol table info available.
#13 0x7fffec106160 in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#14 0x7fffec10620c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
No symbol table info available.
#15 0x74d6fc8f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#16 0x74d186fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#17 0x74b41fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#18 0x72411964 in KDevelop::CompletionWorkerThread::run
(this=0x4574350) at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
No locals.
#19 0x74b46de8 in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#20 0x7fffecc93424 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#21 0x74460cbd in clone () from /usr/lib/libc.so.6
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 362521] New: PEP-3132 not supported
https://bugs.kde.org/show_bug.cgi?id=362521 Bug ID: 362521 Summary: PEP-3132 not supported Product: kdev-python Version: 4.90.91 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: francis.he...@yahoo.co.uk PEP-3132 "Extended Iterable Unpacking" (https://www.python.org/dev/peps/pep-3132/), part of Python 3.0, allows the syntax: `a, *b, c = range(5)` Resulting in a == 0; b == [1,2,3]; c == 4 kdev-python doesn't like this and warns that 'b' is undefined. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 362515] New: Segfault in code completion
https://bugs.kde.org/show_bug.cgi?id=362515
Bug ID: 362515
Summary: Segfault in code completion
Product: kdev-python
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Code completion
Assignee: m...@svenbrauch.de
Reporter: francis.he...@yahoo.co.uk
Built from 5.0 branch as of 10th March, on Arch Linux. KDevelop and
KDevPlatform ditto.
Code being edited:
===
...
class EntityNetwork(dict):
@classmethod
def from_file(cls, filename):
file = open(fi) << partway through typing 'filename'.
Backtrace:
Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa3477700 (LWP 3100)]
0x7fffa3735f16 in
Python::PythonCodeCompletionContext::PythonCodeCompletionContext
(this=0x7fff9c00b980, context=..., text=..., followingText=..., position=...,
depth=)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:1033
1033
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:
No such file or directory.
(gdb) bt full
#0 0x7fffa3735f16 in
Python::PythonCodeCompletionContext::PythonCodeCompletionContext
(this=0x7fff9c00b980, context=..., text=..., followingText=..., position=...,
depth=)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:1033
location =
parser = {m_code = {static null = {}, d = 0xb8},
m_cursorPositionInString = 224}
firstStatus =
currentlyCheckedLine =
from =
importIndex =
beforeAndAfterCursor = {first = {static null = {}, d =
0x1c}, second = {static null = {}, d = 0x6000c}}
indents = {m_indents = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x7fffa3476500}, d = 0x7fffa3476500}}}
currentlyChecked =
defKeywords = {>
= {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x7fffa34765d0}, d = 0x7fffa34765d0}}
import =
fromIndex =
textWithoutStrings = {static null = {}, d = 0x18}
allExpressions = {> =
{> = {}, {p =
{static shared_null = {ref = {atomic = {_q_value = {> =
{
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x3}, d = 0x3}},
m_internalPtr = 12}
__PRETTY_FUNCTION__ =
"Python::PythonCodeCompletionContext::PythonCodeCompletionContext(KDevelop::DUContextPointer,
const QString&, const QString&, const KDevelop::CursorInRevision&, int, const
Python::PythonCodeCompletionW"...
#1 0x7fffa373bc07 in
Python::PythonCodeCompletionWorker::createCompletionContext (this=0x45944c0,
context=..., contextText=..., followingText=..., position=...)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/worker.cpp:47
completionContext =
#2 0x724090d0 in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x45944c0, context=..., position=..., followingText=...,
contextRange=..., contextText=...)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:153
__PRETTY_FUNCTION__ = "virtual void
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUContextPointer,
const KTextEditor::Cursor&, QString, const KTextEditor::Range&, const
QString&)"
completionContext = {d = 0x4ca22f0}
#3 0x72408772 in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x45944c0, context=..., position=..., view=0x4abbe10)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:129
foreground = {m_locked = false}
doc = 0x4ca22f0
__PRETTY_FUNCTION__ = "void
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUContextPointer,
const KTextEditor::Cursor&, KTextEditor::View*)"
range = {m_start = {m_line = 67, m_column = 0}, m_end = {m_line = 67,
m_column = 20}}
text = {static null = {}, d = 0x7fff9c00c5a0}
cursorPosition = {m_line = 67, m_column = 21}
followingText = {static null = {}, d = 0x7fff9c008200}
#4 0x7240f232 in QtPrivate::FunctorCall, QtPrivate::List,
KTextEditor::Cursor const&, KTextEditor::View*>, void, void
(KDevelop::CodeCompletionWorker::*)(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*)>::call (arg=,
o=, f=)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:501
No locals.
#5 QtPrivate::FunctionPointer,
KTextEditor::Cursor const&,
KTextEditor::View*)>::call,
KTextEditor::Cursor const&, KTextEditor::View*>, void> (arg=,
o=, f=
[Breeze] [Bug 361612] gtk3 Breeze theme contains lots of deprecation errors
https://bugs.kde.org/show_bug.cgi?id=361612 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #1 from Francis Herne --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=361066 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file
https://bugs.kde.org/show_bug.cgi?id=344192 --- Comment #4 from Francis Herne --- It seems to me as though Kate should crash the same way, but I can't make it do so. It does behave in a really unintuitive way that probably should be its own bug, but doesn't actually crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file
https://bugs.kde.org/show_bug.cgi?id=344192
--- Comment #3 from Francis Herne ---
It crashes intermittently with those flags (or all the Qt::QueuedConnection
flags around there) removed, but not every time as before.
I'm a bit busy actually using KDevelop to poke inside it much, maybe later this
week.
Backtrace looks different again...
Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
#0 0x71c70040 in
QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) ()
from /usr/lib/libQt5Qml.so.5
#1 0x74d46260 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#2 0x705654d2 in KParts::Part::setWindowCaption(QString const&) ()
from /usr/lib/libKF5Parts.so.5
#3 0x7056c030 in KParts::ReadWritePart::saveAs(QUrl const&) () from
/usr/lib/libKF5Parts.so.5
#4 0x708b9545 in KTextEditor::DocumentPrivate::saveAs (this=0x9f9e50,
url=...) at
/home/flh/ktexteditor/src/ktexteditor-5.20.0/src/document/katedocument.cpp:5443
url = @0x7fffd4d0: {d = 0x116c130}
this = 0x9f9e50
#5 0x708b9ab9 in KTextEditor::DocumentPrivate::documentSaveAs
(this=0x9f9e50) at
/home/flh/ktexteditor/src/ktexteditor-5.20.0/src/document/katedocument.cpp:4277
saveUrl = {d = 0x116c130}
#6 0x70a62deb in KTextEditor::DocumentPrivate::qt_static_metacall
(_o=, _c=, _id=,
_a=0x7fffd6b0) at
/home/flh/ktexteditor/src/build/src/moc_katedocument.cpp:501
_r =
_t =
#7 0x74d46870 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#8 0x75a353d2 in QAction::triggered(bool) () from
/usr/lib/libQt5Widgets.so.5
#9 0x75a37ef0 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQt5Widgets.so.5
#10 0x75a3884f in QAction::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#11 0x75a3e68c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x75a438f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x74d1a518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7528f826 in QShortcutMap::dispatchEvent(QKeyEvent*) () from
/usr/lib/libQt5Gui.so.5
#15 0x7528f8d9 in QShortcutMap::tryShortcut(QKeyEvent*) () from
/usr/lib/libQt5Gui.so.5
#16 0x75248716 in QWindowSystemInterface::handleShortcutEvent(QWindow*,
unsigned long, int, QFlags, unsigned int, unsigned int,
unsigned int, QString const&, bool, unsigned short) ()
from /usr/lib/libQt5Gui.so.5
#17 0x75260a14 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /usr/lib/libQt5Gui.so.5
#18 0x75265b65 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/libQt5Gui.so.5
#19 0x75242d6b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#20 0x7fffd7b53d10 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#21 0x7fffec0f0d87 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#22 0x7fffec0f0fe0 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x7fffec0f108c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#24 0x74d6fc8f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#25 0x74d186fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#26 0x74d20b7c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#27 0x0040cbfa in main (argc=1, argv=) at
/tmp/yaourt-tmp-flh/aur-kdevelop-git/src/kdevelop/app/main.cpp:680
timer = {t1 = -9223372036854775808, t2 = -9223372036854775808}
description = "The KDevelop Integrated Development Environment"
aboutData = {d = 0x63b240}
debugArgs = {
[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file
https://bugs.kde.org/show_bug.cgi?id=344192
Francis Herne changed:
What|Removed |Added
CC||francis.he...@yahoo.co.uk
--- Comment #1 from Francis Herne ---
This still causes a crash in 4.90.91 and the current 5.0 branch, albeit
slightly different.
When saving the second file, the "Overwrite <-> Cancel" dialog is shown. When
choosing 'Overwrite', KDevelop crashes iff the first file has unsaved changes.
--
Thread 1 "kdevelop" received signal SIGABRT, Aborted.
0x743ab2a8 in raise () from /usr/lib/libc.so.6
#0 0x743ab2a8 in raise () from /usr/lib/libc.so.6
#1 0x743ac72a in abort () from /usr/lib/libc.so.6
#2 0x747a87cd in __gnu_cxx::__verbose_terminate_handler () at
/build/gcc/src/gcc-5-20160209/libstdc++-v3/libsupc++/vterminate.cc:95
terminating = true
t =
#3 0x747a6636 in __cxxabiv1::__terminate (handler=) at
/build/gcc/src/gcc-5-20160209/libstdc++-v3/libsupc++/eh_terminate.cc:47
No locals.
#4 0x747a6681 in std::terminate () at
/build/gcc/src/gcc-5-20160209/libstdc++-v3/libsupc++/eh_terminate.cc:57
No locals.
#5 0x747a71bf in __cxxabiv1::__cxa_pure_virtual () at
/build/gcc/src/gcc-5-20160209/libstdc++-v3/libsupc++/pure.cc:50
No locals.
#6 0x77a915e3 in KDevelop::MainWindow::updateTabColor (this=0xa00340,
doc=0xa3db90) at
/tmp/yaourt-tmp-flh/aur-kdevplatform-git/src/kdevplatform/shell/mainwindow.cpp:420
color = {cspec = 11142656, ct = {argb = {alpha = 0, red = 0, green = 0,
blue = 0, pad = 0}, ahsv = {alpha = 0, hue = 0, saturation = 0, value = 0, pad
= 0}, acmyk = {alpha = 0, cyan = 0, magenta = 0, yellow = 0,
black = 0}, ahsl = {alpha = 0, hue = 0, saturation = 0, lightness
= 0, pad = 0}, array = {0, 0, 0, 0, 0}}}
doc = 0xa3db90
this = 0xa00340
#7 0x74d46659 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#8 0x75a81c4b in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#9 0x75b940db in QMainWindow::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#10 0x702abd9a in KMainWindow::event(QEvent*) () from
/usr/lib/libKF5XmlGui.so.5
#11 0x702fb1c5 in KXmlGuiWindow::event(QEvent*) () from
/usr/lib/libKF5XmlGui.so.5
#12 0x75a3d68c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#13 0x75a428f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#14 0x74d19518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#15 0x74d1b3da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#16 0x74d6e883 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fffec0eed87 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x7fffec0eefe0 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x7fffec0ef08c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x74d6ec8f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#21 0x74d176fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#22 0x74d1fb7c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#23 0x0040cbfa in main (argc=1, argv=) at
/tmp/yaourt-tmp-flh/aur-kdevelop-git/src/kdevelop/app/main.cpp:680
timer = {t1 = -9223372036854775808, t2 = -9223372036854775808}
description = "The KDevelop Integrated Development Environment"
aboutData = {d = 0x63b6b0}
debugArgs = {> = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x74dc8d40 }, d =
0x74dc8d40 }}, }
debugeeName = {static null = {}, d = 0x74dc6ee0
}
app = { = {}, }
migrator = {d = 0x692e40}
__PRETTY_FUNCTION__ = "int main(int, char**)"
parser = {d = 0x6a96b0}
initialFiles = {d = 0x74dc6ee0 }
session = {static null = {}, d = 0x74dc6ee0
}
nRunningSessions =
splash =
core = 0xbe45c0
projectNames = {> = {> =
{}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x74dc8d40 }, d =
0x74dc8d40 }}, }
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 331137] git->Show Differences closes file
https://bugs.kde.org/show_bug.cgi?id=331137 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #4 from Francis Herne --- This doesn't happen (AFAICT) with KDevelop 4.90.91 or current 5.0 branch. The tab remains open when leaving the diff view. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356012] Wish: Extra whitespace should be highlighted in git diff output
https://bugs.kde.org/show_bug.cgi?id=356012 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #1 from Francis Herne --- The setting 'highlight trailing spaces' (Editor -> Appearance -> Whitespace Highlighting) applies to the diff view. The appearance isn't so conspicuous by default, but you can change the colour 'Tab and Space Markers' to something colourful. Additionally, setting 'Remove trailing spaces' (Editor -> Open/Save -> Automatic Cleanups on Save) to an option that isn't "Never" will prevent the whitespace from existing in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360418] Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418
--- Comment #2 from Francis Herne ---
Moving, since this occurs with KWrite and KDevelop.
KTextEditor compiled with debug symbols:
[20:50][436][flh ~/]$ cat kate_out
Thread 1 "kate" received signal SIGSEGV, Segmentation fault.
0x7799ec7b in KateVi::EmulatedCommandBar::executeCommand
(this=this@entry=0xbad790, commandToExecute=...) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/emulatedcommandbar.cpp:1142
1142if (range.isValid() && !p->supportsRange(cmd)) {
#0 0x7799ec7b in KateVi::EmulatedCommandBar::executeCommand
(this=this@entry=0xbad790, commandToExecute=...) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/emulatedcommandbar.cpp:1142
p = 0x0
ci =
n =
textlen =
commandResponseMessage = {static null = {}, d =
0x732eba20 }
cmd = {static null = {}, d = 0xe179e0}
range = {m_start = {m_line = 0, m_column = 0}, m_end = {m_line = 0,
m_column = 0}}
#1 0x779a1d98 in KateVi::EmulatedCommandBar::handleKeyPress
(this=0xbad790, keyEvent=keyEvent@entry=0x7fffd100) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/emulatedcommandbar.cpp:1036
commandToExecute = {static null = {}, d = 0xe2df90}
parsedSedExpression = {parsedSuccessfully = false, findBeginPos = 0,
findEndPos = -225121536, replaceBeginPos = 32767, replaceEndPos = 64, delimiter
= {ucs = 0}}
commandResponseMessage = {static null = {}, d = 0x6}
#2 0x7798d5fd in KateVi::InputModeManager::handleKeypress
(this=0x14727d0, e=0x7fffd100) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/inputmodemanager.cpp:147
res = false
keyIsPartOfMapping = false
isSyntheticSearchCompletedKeyPress = false
#3 0x7323ade4 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#4 0x748b60fe in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#5 0x748bb6d4 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#6 0x7323b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#7 0x7798da06 in QCoreApplication::sendEvent (event=0x7fffd100,
receiver=) at /usr/include/qt/QtCore/qcoreapplication.h:227
No locals.
#8 KateVi::InputModeManager::feedKeyPresses (this=0x14727d0, keyPresses=...)
at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/inputmodemanager.cpp:235
decoded = {static null = {}, d = 0x121e5a0}
k =
destWidget =
_container_ = {c = {static null = {}, d = 0x121d700}, i
= 0x121d718, e = 0x121d71a, control = 1}
key =
mods = {i = 0}
text = {static null = {}, d = 0x732eba20
}
#9 0x779a4314 in KateVi::KeyMapper::playBackRejectedKeys
(this=this@entry=0xe31e80) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/keymapper.cpp:69
mappingKeys = {static null = {}, d = 0x121d700}
#10 0x779a470e in KateVi::KeyMapper::handleKeypress (this=0xe31e80,
key=..., key@entry=...) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/keymapper.cpp:122
isPartialMapping =
isFullMapping =
#11 0x7798d590 in KateVi::InputModeManager::handleKeypress
(this=0x14727d0, e=0x7fffda70) at
/home/flh/ktexteditor/src/ktexteditor-5.19.0/src/vimode/inputmodemanager.cpp:133
key = {ucs = 57424}
res = false
keyIsPartOfMapping = false
isSyntheticSearchCompletedKeyPress = false
#12 0x7323ade4 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#13 0x748b60fe in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#14 0x748bb6d4 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#15 0x7323b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#16 0x749202f3 in ?? () from /usr/lib/libQt5Widgets.so.5
#17 0x748b6124 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#18 0x748baf78 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#19 0x7323b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#20 0x7410d1b8 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /usr/lib/libQt5Gui.so.5
#21 0x741124c5 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/libQt5Gui.so.5
#22 0x740f0a1b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#23 0x7fffe4e4c750 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#24 0x7fffee9
[frameworks-ktexteditor] [Bug 360418] Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418 Francis Herne changed: What|Removed |Added Product|kate|frameworks-ktexteditor Version|unspecified |5.19.0 Component|Vi Input Mode |general -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360418] Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418 --- Comment #1 from Francis Herne --- Kate is 15.12.2, KTextEditor is 5.19.0. Latest version in the bugs.kde.org dropdown is '5.0.0', some newer options would be nice. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360418] New: Crash using 'g' in Vi-input mode
https://bugs.kde.org/show_bug.cgi?id=360418 Bug ID: 360418 Summary: Crash using 'g' in Vi-input mode Product: kate Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk When editing a file in vi-input, attempting to go to a specific line crashes Kate (or KDevelop). Reproducible: Always Steps to Reproduce: 1. Enter vi-input mode. 2. Type :42g (or a line number of your choice). 3. Hit 'enter'. Actual Results: Kate segfaults. Expected Results: Cursor moved to specified line. Backtrace. I don't have debug symbols enabled currently, might recompile later. Thread 1 "kate" received signal SIGSEGV, Segmentation fault. 0x779bf408 in KateVi::EmulatedCommandBar::executeCommand(QString const&) () from /usr/lib/libKF5TextEditor.so.5 #0 0x779bf408 in KateVi::EmulatedCommandBar::executeCommand(QString const&) () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #1 0x779c4beb in KateVi::EmulatedCommandBar::handleKeyPress(QKeyEvent const*) () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #2 0x779ad7d9 in KateVi::InputModeManager::handleKeypress(QKeyEvent const*) () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #3 0x7324ade4 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #4 0x748c60fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #5 0x748cb6d4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #6 0x7324b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #7 0x779add2d in KateVi::InputModeManager::feedKeyPresses(QString const&) const () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #8 0x779c704b in KateVi::KeyMapper::playBackRejectedKeys() () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #9 0x779c74e5 in KateVi::KeyMapper::handleKeypress(QChar) () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #10 0x779ad770 in KateVi::InputModeManager::handleKeypress(QKeyEvent const*) () from /usr/lib/libKF5TextEditor.so.5 No symbol table info available. #11 0x7324ade4 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #12 0x748c60fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #13 0x748cb6d4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #14 0x7324b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #15 0x749302f3 in ?? () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #16 0x748c6124 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #17 0x748caf78 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 No symbol table info available. #18 0x7324b03a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #19 0x7411d1b8 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/libQt5Gui.so.5 No symbol table info available. #20 0x741224c5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 No symbol table info available. #21 0x74100a1b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 No symbol table info available. #22 0x7fffe4e5c750 in ?? () from /usr/lib/libQt5XcbQpa.so.5 No symbol table info available. #23 0x7fffee9d3d87 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #24 0x7fffee9d3fe0 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #25 0x7fffee9d408c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #26 0x732a318f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #27 0x7324957a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #28 0x7ff
[frameworks-kwidgetsaddons] [Bug 360061] Colour list squashed vertically.
https://bugs.kde.org/show_bug.cgi?id=360061 --- Comment #3 from Francis Herne --- Ah, no it isn't. Just with Breeze. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356638] False-positive warning with addEventListener()
https://bugs.kde.org/show_bug.cgi?id=356638
--- Comment #4 from Francis Herne ---
Whoops, missed a semicolon on the first line.
In fact, KDevelop doesn't like having an object as the second argument either
(contrary to what my original report implies).
var listener = {
handleEvent: function(event) {}
};
var el = document.getElementById('elephant');
el.addEventListener("click", listener, false);
is also flagged as an error. I think the parser is being too picky about what
can be an EventListener, given JS's duck typing and lack of inheritance (before
ES6).
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 356638] False-positive warning with addEventListener()
https://bugs.kde.org/show_bug.cgi?id=356638
--- Comment #3 from Francis Herne ---
The 13-line example on the linked page
(https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#JavaScript_Content)
encounters it.
Cut down further:
function someFunction() {}
var el = document.getElementById('elephant');
el.addEventListener("click", someFunction, false);
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209
--- Comment #8 from Francis Herne ---
I compiled KDevPlatform with debug symbols, but the site didn't want me to
upload 63MB of backtrace.
Snipping out the middle quarter-million lines, which AFAICT are pretty much
identical:
#0 KDevelop::ItemRepository,
KDevelop::QualifiedIdentifierItemRequest, true, true, 0u, 1048576u>::index
(this=0x2cce220, request=...) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/serialization/itemrepository.h:1100
__PRETTY_FUNCTION__ = "unsigned int KDevelop::ItemRepository::index(const ItemRequest&) [with Item =
KDevelop::QualifiedIdentifie"...
lock = {m_mutex = 0x2ace1a0}
size =
bucketInChainWithSpace =
lastBucketWalked =
pickedBucketInChain =
useBucket =
reOrderFreeSpaceBucketIndex =
#1 0x724e26bd in KDevelop::QualifiedIdentifier::makeConstant
(this=0x7f7ff1d0) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/identifier.cpp:1133
this = 0x7f7ff1d0
#2 0x724e2859 in KDevelop::QualifiedIdentifier::index
(this=0x7f7ff1d0) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/identifier.cpp:620
No locals.
#3 0x724e288c in
KDevelop::IndexedQualifiedIdentifier::IndexedQualifiedIdentifier
(this=0x7f7ff1c0, id=...) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/identifier.cpp:1455
No locals.
#4 0x724c80e8 in KDevelop::Declaration::id (this=,
forceDirect=) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/declaration.cpp:570
No locals.
#5 0x724a05ab in KDevelop::DUContext::indexedImporters
(this=0x7fffc0043ff0) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/ducontext.cpp:860
ret = {> = {a = 256, s
= 0, ptr = 0x7f7ffad0, {array =
"0\f\200\377\377\177\000\000\000\000\000\000\000\000\000\000pU\363\364\377\177\000\000\001\000\000\000\000\000\000\000\220\003\200\377\377\177\000\000\000g\237f\255\244k\324X\333\310\362\377\177\000\000X\303\377\377\377\177\000\000\060\f\200\377\377\177\000\000\360\230\a\300\377\177\000\000
P\t\300\377\177\000\000\000\000\000\000\000\000\000\000\220\003\200\377\377\177\000\000\071\214P\362\377\177\000\000
\032\t\300\377\177\000\000p\373\177\377\377\177\000\000\060jo\003\000\000\000\000\307\177\314\364\377\177\000\000\200$\210\362\377\177\000\000X\303\377\377\377\177\000\000\001\000\000\000\004",
'\000' ,
"\001\000\000\003\000\000\000\220\373\177\377\377\177\000\000\001\000\000\000\002\000\000\000"...,
q_for_alignment_1 = 140737479969840, q_for_alignment_2 =
6.9533553935368499e-310}}, }
#6 0x72508ae5 in getInheritersInternal (decl=0x7fffc00798f0,
maxAllowedSteps=@0x7fffc358: 4294872234,
collectVersions=collectVersions@entry=false) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/duchainutils.cpp:496
_container_ = {c = {>
= {a = -8387840, s = 32767, ptr = 0x724a060f
, {array =
"\024\000\001\000\000\000\000\000\000LR\362\000\000\000\000\000\001\000\000\000\000\000\000\000\003\200\377\377\177\000\000@\003\200\377\377\177\000\000\300\326,\003\000\000\000\000\300\003\200\377\377\177\000\000
\253H\363\377\177\000\000\002\000\001\000\377\177\000\000\021\201L\362\377\177",
'\000' , "\024\000\001", '\000' ,
"\200\377\177\000\000\000g\237f\255\244k\324\001\000\000\000\000\000\000\000@\f\200\377\377\177\000\000@\f\200\377\377\177\000\000\000g\237f\255\244kԠ\003\200\377\377\177\000\000@\f\200\377\377\177\000\000\000\001\000\000\003\000\000\000\240\003\200\377\377\177\000\000\001\000\000\000\002\000\000\000\001"...,
q_for_alignment_1 = 65556, q_for_alignment_2 = 3.2388967478768758e-319}}, }, i = 0x7fffc00b5750, e = 0x1, control = -8381200}
ret = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74f35560
}, d = 0x74f35560 }}
#7 0x72508a9c in getInheritersInternal
(decl=decl@entry=0x7fffc0091830, maxAllowedSteps=@0x7fffc358: 4294872234,
collectVersions=collectVersions@entry=true) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/duchainutils.cpp:523
a = 0
count = 1
allDeclarations = 0x7fffc02b3ede
ret = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74f35560
}, d = 0x74f35560 }}
#8 0x7250964a in KDevelop::DUChainUtils::getInheriters
(decl=decl@entry=0x7fffc0091830, maxAllowedSteps=@0x7fffc358: 4294872234,
collectVersions=collectVersions@entry=true) at
/home/flh/kdevplatform/src/kdevplatform-4.90.91/language/duchain/duchainutils.cpp:536
inheriters = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d =
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209 --- Comment #7 from Francis Herne --- Created attachment 97758 --> https://bugs.kde.org/attachment.cgi?id=97758&action=edit Tooltip showing 'Overriders possible'. Tooltip showing with link that shouldn't exist, and that crashes KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209 Francis Herne changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #6 from Francis Herne --- I do, see attachment. I've tried deleting .cache/kdevduchain, creating a new session, copied the file to a new account and opened it there. Same thing still happens. :-/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209
--- Comment #4 from Francis Herne ---
Well, that was simpler than I expected!
Very-reduced test case:
struct Foo {
union {} bar;
virtual void SomeFunction() {}
};
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209 Francis Herne changed: What|Removed |Added Component|Language Support: CPP |Language Support: CPP ||(Clang-based) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209 --- Comment #1 from Francis Herne --- Memory, rather. Glad I don't have any swap... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360209] New: Crash with 'Overriders possible, show all'
https://bugs.kde.org/show_bug.cgi?id=360209
Bug ID: 360209
Summary: Crash with 'Overriders possible, show all'
Product: kdevelop
Version: 4.90.91
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Language Support: CPP
Assignee: kdevelop-bugs-n...@kde.org
Reporter: francis.he...@yahoo.co.uk
When selecting 'Overriders possible, show all' on the line:
'virtual void UpdateDeltaXY(Direction direction) {}'
KDevelop crashes, apparently by recursing in
KDevelop::DUChainUtils::getOverriders() until it runs out of stack.
Backtrace:
#0 0x74589b69 in _int_malloc () from /usr/lib/libc.so.6
#1 0x7458b924 in malloc () from /usr/lib/libc.so.6
#2 0x74941de8 in operator new (sz=72) at
/build/gcc/src/gcc-5-20160209/libstdc++-v3/libsupc++/new_op.cc:50
#3 0x725144c9 in KDevelop::QualifiedIdentifier::prepareWrite() () from
/usr/lib/libKDevPlatformLanguage.so.10
#4 0x72514648 in
KDevelop::QualifiedIdentifier::push(KDevelop::IndexedIdentifier const&) () from
/usr/lib/libKDevPlatformLanguage.so.10
#5 0x724fb65e in KDevelop::Declaration::qualifiedIdentifier() const ()
from /usr/lib/libKDevPlatformLanguage.so.10
#6 0x724fc3c9 in KDevelop::Declaration::id(bool) const () from
/usr/lib/libKDevPlatformLanguage.so.10
#7 0x724d6f0b in KDevelop::DUContext::indexedImporters() const () from
/usr/lib/libKDevPlatformLanguage.so.10
#8 0x72532028 in ?? () from /usr/lib/libKDevPlatformLanguage.so.10
#9 0x72531fce in ?? () from /usr/lib/libKDevPlatformLanguage.so.10
#10 0x72532609 in
KDevelop::DUChainUtils::getInheriters(KDevelop::Declaration const*, unsigned
int&, bool) () from /usr/lib/libKDevPlatformLanguage.so.10
#11 0x72532f7f in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#12 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#13 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#14 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#15 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#16 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47544 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47545 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47546 0x72533117 in
KDevelop::DUChainUtils::getOverriders(KDevelop::Declaration const*,
KDevelop::Declaration const*, unsigned int&) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47547 0x725a6710 in
KDevelop::AbstractDeclarationNavigationContext::htmlAdditionalNavigation() ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47548 0x725a9f34 in
KDevelop::AbstractDeclarationNavigationContext::html(bool) () from
/usr/lib/libKDevPlatformLanguage.so.10
#47549 0x72599a31 in KDevelop::AbstractNavigationWidget::update() ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47550 0x7259a097 in
KDevelop::AbstractNavigationWidget::setContext(QExplicitlySharedDataPointer,
int) ()
from /usr/lib/libKDevPlatformLanguage.so.10
#47551 0x7259a321 in
KDevelop::AbstractNavigationWidget::anchorClicked(QUrl const&) () from
/usr/lib/libKDevPlatformLanguage.so.10
#47552 0x74ec46cd in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/libQt5Core.so.5
#47553 0x75d676d5 in QTextBrowser::anchorClicked(QUrl const&) () from
/usr/lib/libQt5Widgets.so.5
#47554 0x75d67d1b in ?? () from /usr/lib/libQt5Widgets.so.5
#47555 0x75d694ed in ?? () from /usr/lib/libQt5Widgets.so.5
#47556 0x74ec43cf in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/libQt5Core.so.5
#47557 0x75d802e5 in QWidgetTextControl::linkActivated(QString const&)
() from /usr/lib/libQt5Widgets.so.5
#47558 0x75d86bcc in ?? () from /usr/lib/libQt5Widgets.so.5
#47559 0x75d87ae5 in ?? () from /
[kdevelop] [Bug 360203] New: 'open!' command opens already-open file.
https://bugs.kde.org/show_bug.cgi?id=360203 Bug ID: 360203 Summary: 'open!' command opens already-open file. Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk When using the GUI file selector, attempting to open an already-opened file switches to that tab and doesn't create a new one. The 'open!' command from kdevplatform_shell_environment instead opens the file in a new tab, causing multiple instances of the same file to be displayed. This leads to another glitch; indicators (unsaved-changes etc.) for a file are only shown in one of its tabs. If that tab is closed, indicators are not shown for the file at all; the remaining tabs only ever contain the filename. I thought I also saw this happen using the GUI file dialog, but I've not been able to reproduce that. Probably I was mistaken. Reproducible: Always Steps to Reproduce: 1. Open a file in KDevelop 2. Open the same file from konsolepart by 'open! path/to/file.ext'. --- 3. Make changes to that file without saving 4. Close the tab containing the unsaved-changes indicator Actual Results: 1-2: File is reopened in a new tab, resulting in two tabs for the same file. --- 3: Unsaved-changes indicator appears in only one tab. 4: No unsaved-changes indicator visible despite unsaved changes. Expected Results: 1-2: Tab containing file is focused. No new tab created. --- 3-4: Indicators visible in all tabs for a file (or just shouldn't happen). Using KDevelop 4.90.91, Frameworks 5.19.0, Qt 5.6-rc1; all on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #23 from Francis Herne --- This still occurs with 5.5.95 (5.6-beta). Not on every logout here, about one in three. I have traces and a coredump, but they're pretty much identical to those above. Does it really need a dozen reports with backtraces for this to be confirmed? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360081] Attempting to parse text/plain files as C or C++
https://bugs.kde.org/show_bug.cgi?id=360081 --- Comment #3 from Francis Herne --- nicolas17 explained more to me on IRC about how mime-type detection works, so "The file _has_ a correct mime-type in the absence of an official NML one." is wrong. I still don't think this is sane, if the filetype detection isn't reliable it should be possible to override it within KDevelop (https://bugs.kde.org/show_bug.cgi?id=360094)? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360094] New: Follow Tools -> Highlighting to select parser, when set by user.
https://bugs.kde.org/show_bug.cgi?id=360094 Bug ID: 360094 Summary: Follow Tools -> Highlighting to select parser, when set by user. Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk At present, the parser to use for a given file is chosen using only KDE's mimetype database. This can fail to detect a filetype, or select an incorrect one, and there's no way for the user to override this. The Tools -> Highlighting menu selects the language for KTextEditor's own highlighting; it's set initially based on the autodetected mimetype but can be overridden by the user. If KDevelop followed this setting when choosing, it would provide the same behaviour as now (I think?) except where the user explicitly set a different mimetype which would presumably be more-correct. Reproducible: Always Steps to Reproduce: 1. Open something with the wrong file-type autodetected. (e.g. NML files as per https://bugs.kde.org/show_bug.cgi?id=360081) 2. Watch KDevelop use the wrong parser on it, with no means to override. 3. Set Tools -> Highlighting to the correct file-type. Actual Results: KDevelop ignores the setting and continues to use the wrong parser. Expected Results: KDevelop follows the setting, and uses a different (correct) parser or none at all. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360081] Attempting to parse text/plain files as C or C++
https://bugs.kde.org/show_bug.cgi?id=360081 Francis Herne changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Francis Herne --- $ file --mime-type road_vehicle_properties.pynml road_vehicle_properties.pynml: text/plain $ kmimetypefinder5 road_vehicle_properties.pynml text/x-csrc This is definitely a bug IMO. The file _has_ a correct mime-type in the absence of an official NML one. Failing that, this would presumably happen for a plain-text README with a lot of C examples in it. KDevelop is producing the incorrect one from thin air (or rather flaky parsing) and then using it to do the wrong thing without prompting or an option to prevent that. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 347449] Attempting to parse non-python files
https://bugs.kde.org/show_bug.cgi?id=347449 --- Comment #5 from Francis Herne --- Sorry, looking at the same problem now it seems to be caused by the C++ parser, so I was probably mistaken when filing this. Re-filed against the C++ parser as https://bugs.kde.org/show_bug.cgi?id=360081 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360081] New: Attempting to parse text/plain files as C or C++
https://bugs.kde.org/show_bug.cgi?id=360081 Bug ID: 360081 Summary: Attempting to parse text/plain files as C or C++ Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk (Reported incorrectly by me before as https://bugs.kde.org/show_bug.cgi?id=347449, it's actually the C++ parser doing this). "NewGRF Meta-Language" files have extension '.nml' and mimetype 'text/plain', and have a superficially C-like syntax. '.pynml' files are similar. KDevelop 4.90.91 attempts to parse them as C++ files, and puts error highlights on almost every line. This makes them quite irritating to read. NML, parsed as C(++?): https://dev.openttdcoop.org/projects/nml/repository/raw/examples/road_vehicle/example_road_vehicle.nml PyNML, parsed as C++: https://dev.openttdcoop.org/projects/road-hog/repository/raw/src/templates/road_vehicle_properties.pynml Reproducible: Always Steps to Reproduce: 1. Open NML or PyNML file. Actual Results: File and problems view filled with errors and warnings. Expected Results: File not parsed, because it's not C or C++. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360080] New: KRunner: Separator line below selection not ideal
https://bugs.kde.org/show_bug.cgi?id=360080 Bug ID: 360080 Summary: KRunner: Separator line below selection not ideal Product: plasmashell Version: 5.5.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: francis.he...@yahoo.co.uk CC: plasma-b...@kde.org Trivial, I know... When the item immediately above a separator line in KRunner is selected, the grey separator line is directly adjacent to the lower border of the blue* selection rectangle. This makes the border look thick or shadowed, and leaves stray-looking pixels at each side because of the radiused corners of the selection. In contrast, when the item _below_ the separator is selected, the separator is hidden. This looks nicer. Comparative screenshot attached. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360080] KRunner: Separator line below selection not ideal
https://bugs.kde.org/show_bug.cgi?id=360080 --- Comment #1 from Francis Herne --- Created attachment 97681 --> https://bugs.kde.org/attachment.cgi?id=97681&action=edit Selection of item above and below separator line -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360070] Splash screen glitch with external monitor
https://bugs.kde.org/show_bug.cgi?id=360070 --- Comment #1 from Francis Herne --- Created attachment 97679 --> https://bugs.kde.org/attachment.cgi?id=97679&action=edit Doodle of how splash screens are shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360070] New: Splash screen glitch with external monitor
https://bugs.kde.org/show_bug.cgi?id=360070 Bug ID: 360070 Summary: Splash screen glitch with external monitor Product: plasmashell Version: 5.5.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: francis.he...@yahoo.co.uk CC: plasma-b...@kde.org This occurs with 5.5.95 (5.6 beta), but also with 5.5.x and maybe earlier. I have a 1600x900 laptop screen, and a 1280x1024 external monitor positioned above and centered. I use 'startkde' from .xinitrc, rather than using a login manager. The splash screen displays correctly on the external monitor. For the first few seconds, the laptop screen displays a 1280px-wide splash screen on the left, with the height apparently correct (logo/progress bar vertically-centered). The remaining space is taken up by part of another splash instance. The logo of this is too high on the screen (sized for the taller external monitor?). My doodle of the appearance is attached. After a few seconds, about when the sliding-in animation completes, the splash screen is redrawn at the correct resolution and everything looks very nice from then on. :-) There are no usability problems, it just looks ugly. Reproducible: Always Steps to Reproduce: 1. Have displays with sizes/positions as described (possibly in other ways also). 2. Start KDE. 3. Watch the splash screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360061] Colour list squashed vertically.
https://bugs.kde.org/show_bug.cgi?id=360061 --- Comment #1 from Francis Herne --- Created attachment 97672 --> https://bugs.kde.org/attachment.cgi?id=97672&action=edit Same screenshot, not on imgur -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360061] New: Colour list squashed vertically.
https://bugs.kde.org/show_bug.cgi?id=360061 Bug ID: 360061 Summary: Colour list squashed vertically. Product: systemsettings Version: 5.5.95 Platform: Archlinux Packages URL: https://i.imgur.com/v5OkseD.png OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: francis.he...@yahoo.co.uk CC: jpwhit...@kde.org In SystemSettings 5.5.95 (5.6 beta), using the kde-unstable packages from Arch: The rows of the colour list are sized to the text. This makes the view/edit boxes on the right extremely thin, which is ugly and makes comparing /setting colours difficult. See the linked screenshot. Reproducible: Always Steps to Reproduce: 1. Open the 'Application Colour Scheme' KCM 2. Go to the 'Colors' tab (localisation bug...) 3. Observe ugly list. Actual Results: List rows are sized to text and almost unpadded. Colour view/edit boxes on the right are squashed. Expected Results: Rows have some padding, boxes are a reasonable size. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359933] Quick Open and Outline dropdowns behave unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=359933 Francis Herne changed: What|Removed |Added Summary|Quick Open and Outline |Quick Open and Outline |popups behave unexpectedly. |dropdowns behave ||unexpectedly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359933] New: Quick Open and Outline popups behave unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=359933 Bug ID: 359933 Summary: Quick Open and Outline popups behave unexpectedly. Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI: all modes Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk When entering text in a toolbar widget, there's a typical behaviour pattern for completion-list dropdowns: - Entries are highlighted when moused-over, and chosen when clicked on. - Up/down arrows highlight the previous/next entry in the dropdown. 'Tab' selects the next entry. 'Enter' chooses the highlighted entry. - The dropdown is hidden when an entry has been chosen. - The dropdown is hidden when clicking anywhere outside it, including in the textbox or on the toolbar. E.g. Dolphin and KDE filepicker pathname boxes, KDevelop documentation search box, GIMP brush selection, [...]. More generally, this is the expected behaviour for any dropdown on a toolbar item (e.g. KDevelop forward/back/code buttons). The Quick Open and Outline entry boxes behave very differently: - Clicking on the dropdown hides it. - Including the scrollbar handle and arrows! - Moused-over elements aren't highlighted, nor are they chosen when clicked on (that hides the dropdown...) - Clicking on the textbox, the toolbar, or various other UI elements doesn't hide the dropdown. Clicking in the editor panel or inside a toolview does. Up/down/tab/enter do behave as normal. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 --- Comment #6 from Francis Herne --- Sorry, yes, I must have done something wrong. Latest patch works for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 --- Comment #4 from Francis Herne --- I tried the patch (compiling KWin made my laptop's fan rather unhappy, not to mention my ears). Unfortunately there was no noticeable change; decorations still appear when unmaximising the window. xprop output is attached above. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 --- Comment #3 from Francis Herne --- Created attachment 97561 --> https://bugs.kde.org/attachment.cgi?id=97561&action=edit diff to after maximising/unmaximising (with border added) After maximising and unmaximising, a border is added and xprop's output changes slightly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 --- Comment #2 from Francis Herne --- Created attachment 97560 --> https://bugs.kde.org/attachment.cgi?id=97560&action=edit xprop output, before maximising (no border) Output of running xprop on a gitg window under KWin, before maximising the window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359797] New: BorderlessMaximizedWindows=true forces server-side decorations
https://bugs.kde.org/show_bug.cgi?id=359797 Bug ID: 359797 Summary: BorderlessMaximizedWindows=true forces server-side decorations Product: kwin Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk Applications with client-side decorations shouldn't have server-side decorations drawn (unless the script for that is enabled), because the double titlebar wastes space and looks broken. With the setting BorderlessMaximisedWindows false or unset, this is the case. When set to 'true', maximising and then unmaximising a window gives it server-side decorations even if it didn't originally have them. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 355260] AutoBrace extension has strange behaviour for several braces compared to parenthesis or brackets
https://bugs.kde.org/show_bug.cgi?id=355260 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #1 from Francis Herne --- This works for me using Kate 15.12.2, KatePart 5.19.0. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 359763] New: Completion in block-selection mode only affects first line, selects preceding content
https://bugs.kde.org/show_bug.cgi?id=359763 Bug ID: 359763 Summary: Completion in block-selection mode only affects first line, selects preceding content Product: frameworks-ktexteditor Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk Created attachment 97542 --> https://bugs.kde.org/attachment.cgi?id=97542&action=edit Montage of screenshots illustrating the problem When in block-selection mode with the cursor spanning multiple lines, normal editing changes each line identically. Picking a completion option, however, completes only the first line. After the completion the first part of the completed word is selected on all lines, so that continuing to enter text produces gibberish. The screenshot is probably clearer than my explanation. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359441] "Deleted by another program" -> "Close" option doesn't.
https://bugs.kde.org/show_bug.cgi?id=359441 --- Comment #1 from Francis Herne --- Correction: "is changed on-disk" should be "is moved or deleted". Changing it in place leads to a slightly different dialog, which works fine. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359441] New: "Deleted by another program" -> "Close" option doesn't.
https://bugs.kde.org/show_bug.cgi?id=359441 Bug ID: 359441 Summary: "Deleted by another program" -> "Close" option doesn't. Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk When a file being edited is changed on-disk by another program, a popup is displayed with the following options: - Save File As - Ignore Changes - Close - Cancel The third option should close the file in question. This works in Kate 15.12, but not in KDevelop 4.90.91; instead, the file remains open and the warning icon disappears from the tab. This causes that file to appear as normal in the UI, with no changed-on-disk or unsaved-changes indicator, but 'disappear' on exit unless new changes are made and saved (in which case the file is silently recreated). Reproducible: Always Steps to Reproduce: 1. Create and save a file. 2. Using another program, delete or move that file on-disk while keeping it open in KDevelop. 3. When returning to the file in KDevelop, select 'Close'. Actual Results: - The file remains open in apparently-normal state. - The file remains deleted on disk if no further changes are made. - The fIle is silently recreated if new changes are made and saved. Expected Results: The file (or the tab showing it) is closed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358907] New: Literal ampersands in toolview context-menu titles.
https://bugs.kde.org/show_bug.cgi?id=358907 Bug ID: 358907 Summary: Literal ampersands in toolview context-menu titles. Product: kdevelop Version: 4.90.91 Platform: Archlinux Packages URL: http://i.cubeupload.com/xuS13m.png OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI: toplevel window Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk When right-clicking on any toolview panel, the title of the context-menu contains an '&' character, usually at the beginning but sometimes as the second character. This does not occur for the context-menus of toolbar icons. Presumably these are shortcut markers as per http://doc.qt.io/qt-5.5/qshortcut.html#mnemonic that aren't being handled somewhere. This occurs for at least 4.90.90 and 4.90.91, I vaguely remember 4.7.x being affected too. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358526] New: Freeze and glitches when changing KDE color scheme
https://bugs.kde.org/show_bug.cgi?id=358526 Bug ID: 358526 Summary: Freeze and glitches when changing KDE color scheme Product: kdevelop Version: 4.90.91 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: toplevel window Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk In 4.90.90 and 4.90.91, changing the KDE colour scheme causes KDevelop's window to become unresponsive and stop redrawing. After about 30 seconds it unfreezes, with the new colors mostly used, but the text in tabs retains the original color which can be unreadable if changing dark->light or vice versa. The editor component retains the original colors, but this also occurs in Kate/KWrite and seems reasonable. Reproducible: Always Steps to Reproduce: 1. Start KDevelop 4.90.90+ 2. Change KDE colorscheme (in System Settings). Dark->light or the reverse is most noticeable. 3. Try poking KDevelop. Wait until it unfreezes. Look at it. Actual Results: KDevelop freezes for 30s, not all UI elements use new colorscheme. Expected Results: KDevelop changes colorscheme of all UI elements, remains responsive to input and window resizing. Compiled and run on ArchLinux x86_64, using gcc 5.3.0, with KF 15.08.0 and Qt 5.5.1. Intel graphics. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356638] False-positive warning with addEventListener()
https://bugs.kde.org/show_bug.cgi?id=356638 --- Comment #1 from Francis Herne --- This only seems to happen when the useCapture (third) argument is provided. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356638] New: False-positive warning with addEventListener()
https://bugs.kde.org/show_bug.cgi?id=356638 Bug ID: 356638 Summary: False-positive warning with addEventListener() Product: kdevelop Version: 4.90.90 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: QML/JavaScript Assignee: kdevelop-bugs-n...@kde.org Reporter: francis.he...@yahoo.co.uk https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener addEventListener() can be called with either an object or (IME much more commonly) a function as its second argument. In the latter case, the following error or one similar to it is displayed: Problem in Semantic analysis: Possible type mismatch between the argument type (EventListener) and the value passed as argument (function void ()) -- You are receiving this mail because: You are watching all bug changes.
