https://bugs.kde.org/show_bug.cgi?id=363237
--- Comment #6 from JATothrim <jarmo.tii...@gmail.com> --- (In reply to Sven Brauch from comment #2) > Hmm, can't reproduce the crash but yes, the display is definitely buggy, we > need to look into that. > > But, how did you lose data? Crash recovery should easily be able to restore > all changes to the file in this case ... This is such an old issue, I don't remember anymore. :-/ Recent kdevelop versions: 5.11.230403 (23.04.3) have not crashed anymore for long time by fiddling with the break points. (In reply to Axel Kellermann from comment #5) > (In reply to Igor Kushnir from comment #4) > > (In reply to Piotr Mierzwinski from comment #3) > > > Fixed in Bug 424431 > > Are you sure this bug is really fixed already? Even with the fix for Bug > > 424431, Breakpoints view only synchronizes when the document is saved. See > > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/147#note_89877 > This issue is definitely not resolved. Reopening it. I was supprised this issue is *still* open and that I had an comment here. :-) I have bug-fix/feature request how to solve this: The Core problem persist as of 5.11.230403 (23.04.3): break points are not kept up to date with editing the source. All break points are updated in document when user adds/toggles/removes them. Current behavior of kdevelop is to keep the break point on the exact line number it was set on, even if that source line doesn't exists anymore since the break points were last updated. This very annoying when you add/remove source lines from source file before any enabled break points. But it is better than nothing. My suggestion how to solve this: When break point is set kdevelop should to record the source line *hash* it was set on. When that source line moves, kdevelop can attempt to update the break point line number based on this break point context (the source line hash) If the break point context doesn't match anything in the file it was enabled in kdevelop should *disable* it, as the code user enabled it on is unlikely to exists anymore. When recording new break point context it might be good idea to ignore white-space parts of the source line: This would allow slightly editing the source line and the hash would still match the source line. As last note adding an "Refresh break points" command to the IDE would be nice. -- You are receiving this mail because: You are watching all bug changes.
