[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-22 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 Aetf <7437...@gmail.com> changed: What|Removed |Added Status|VERIFIED|CLOSED --- Comment #27 from Aetf

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-22 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #26 from Ian Haber --- Alright. I posted in the gdb bugtracking https://sourceware.org/bugzilla/show_bug.cgi?id=21192 hopefully they will fix it eventually. -- You are receiving this mail because: You are

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 Aetf <7437...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM --- Comment #25 from Aetf

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #24 from Ian Haber --- would it be possible to maybe have some sort of manually set variable that would be a prefix for member variables? a lot of us use a very specific member variable prefix, so if it starts with

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 Aetf <7437...@gmail.com> changed: What|Removed |Added Attachment #104135|0 |1 is obsolete|

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #22 from Aetf <7437...@gmail.com> --- Okay I can reproduce your issue now. I guess the difference is that yours is multi-threaded (several threads for qt internal stuff). And when gdb stopped, it stopped at another thread different from the

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #21 from Ian Haber --- Created attachment 104158 --> https://bugs.kde.org/attachment.cgi?id=104158=edit Log file for the test case Here is the log file for the test case i created. -- You are receiving this mail

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #20 from Ian Haber --- I have created a simple test program that causes the crash. //main.cpp int main(int argc, char* argv[]) { QApplication applicationInstance(argc, argv); testGDBCrash crasher; if

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #19 from Ian Haber --- ran the test case, it does not give me the same behavior. i'm currently modifying it to see if i can reproduce the issue. As far as i can tell, the only differences between my current version

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #18 from Aetf <7437...@gmail.com> --- Created attachment 104154 --> https://bugs.kde.org/attachment.cgi?id=104154=edit GDB outputs when watchpoint goes out of scope Yes, kdevelop uses plain variable name when adding watch points for

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-21 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #17 from Ian Haber --- The patch does prevent the crash, although as you suggested, gdb is just sitting there hanging now. Messing with the gdb console outside of kdevelop led me to something interesting. if i use

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #16 from Aetf <7437...@gmail.com> --- Created attachment 104135 --> https://bugs.kde.org/attachment.cgi?id=104135=edit Proposed patch -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #15 from Aetf <7437...@gmail.com> --- Okay. So setting watch point itself seems normal in log. The crash actually happens before the watch point was triggered. gdb returned two replies for 35-exec-continue command: 35^running and

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #14 from Milian Wolff --- Please also try valgrind, that is usually much more helpful in such situations: valgrind --smc-check=all-non-file --track-origins=yes kdevelop -- You are receiving this mail because: You are

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #13 from Ian Haber --- Created attachment 104134 --> https://bugs.kde.org/attachment.cgi?id=104134=edit Debug output for debugger Here is the output. my gdb version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #12 from Aetf <7437...@gmail.com> --- I see. Seems your Qt version doesn't support semicolon separated logging rules. Instead, create a file named logging.conf with the following content: [Rules] kdevelop.debuggers.gdb.debug=true

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #11 from Ian Haber --- I get the crash regardless of how i set the breakpoint. i can set it in gdb or through kdevelop and both will crash. the only logging stuff i got was qt.core.logging: Ignoring malformed

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #10 from Aetf <7437...@gmail.com> --- Hmm actually I can't reproduce this. I tried with a structure member variable and it works as intended. >From the log output, kdevelop was complaining about gdb not returning required data. So my

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-20 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #9 from Ian Haber --- with those debug messages, i get the same backtrace as before, but i get QMetaObject::invokeMethod: No such method ExpandingTree::scrollTo(QModelIndex,QAbstractItemView::ScrollHint) Breakpoint

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595 Aetf <7437...@gmail.com> changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #8 from Aetf

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595 Kevin Funk changed: What|Removed |Added CC||7437...@gmail.com -- You are

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #7 from Ian Haber --- if you need anything else from gdb, i still have it up and will get back to you on monday. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #6 from Ian Haber --- here is the backtrace. it also looks like i got a message saying 'breakpoint doesn't contain required location/expression data'. maybe that has something to do with it Thread 1 "kdevelop"

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #5 from Kevin Funk --- True, this got added just recently. I've restored compat with KF5 5.15 now. See: commit 2c775c07436107f90bec8ee16b73f4e5258f362d Author: Kevin Funk Date: Fri Feb 17 23:32:22 2017

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #4 from Ian Haber --- I get this build error when i attempt to build master. what module is KUrlRequester in that i'm assuming i need to add to the list of things to download and update.

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #3 from Kevin Funk --- FWIW, master should build fine according to CI. If you want to switch branches I *think* you should be able to use this: module kdevelop branch-group kf5-qt5 ... If that doesn't work you can still

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #2 from Ian Haber --- so i've never been able to get a backtrace while using the appimage. I attempted to build source today, but it seems there are build errors in master at the moment. how do i set kdesrc-build to

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---