| Summary: | kdevelop crashes when trying to remove breakpoint | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | stompdagger1 |
| Component: | CPP Debugger | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aleixpol, kfunk, niko.sams, olaf.the.lost.viking |
| Priority: | NOR | ||
| Version First Reported In: | 4.4.60 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
stompdagger1
2012-11-26 18:07:59 UTC
#5 0x00007fd0243a1425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007fd0243a4b8b in __GI_abort () at abort.c:91 #7 0x00007fd02574b4c2 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=0x6e785b8 "ASSERT: \"b\" in file /home/krf/devel/src/kdevplatform/debugger/breakpoint/breakpointmodel.cpp, line 127") at global/qglobal.cpp:2290 #8 0x00007fd02574b838 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=0x7fd0258b4f68 "ASSERT: \"%s\" in file %s, line %d", ap=ap@entry=0x7fff46766288) at global/qglobal.cpp:2336 #9 0x00007fd02574b9c4 in qFatal (msg=<optimized out>) at global/qglobal.cpp:2519 #10 0x00007fd0210c3ede in KDevelop::BreakpointModel::markContextMenuRequested (this=0xe62f40, document=<optimized out>, mark=..., pos=..., handled=@0x7fff4676662f: false) at /home/krf/devel/src/kdevplatform/debugger/breakpoint/breakpointmodel.cpp:127 #11 0x00007fd025867f5f in QMetaObject::activate (sender=0x36fa8c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff467665d0) at kernel/qobject.cpp:3547 #12 0x00007fcffc9dfb03 in KateDocument::markContextMenuRequested(KTextEditor::Document*, KTextEditor::Mark, QPoint, bool&) () from /usr/lib/libkatepartinterfaces.so.4 #13 0x00007fcffc9e03e8 in KateDocument::handleMarkContextMenu(int, QPoint) () from /usr/lib/libkatepartinterfaces.so.4 Reproducible. I'll have a look. Did you have a look? :) Yeah, but unfortunately it's non-trivial to fix, I'll try again when I find time. Okay, we simply need to know when a mark has been moved inside a document. When we get such a notifcation, we have to take care of updating BreakpointModel immediately. However, this might be a bit tricky with KTextEditor and friends. There seems to be no easy way to track changes to a MovingCursor instance. I think I just experienced the same (wasn't found by DrKonqi), sorry for duplicate in that case: bug #381312 Additionally, I guess the following bug reporters have the same problem: - bug #334877 - bug #340844 - bug #347529 - bug #348945 - bug #350490 - bug #361693 - bug #363237 - bug #372937 - bug #377995 Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |