Initialize breakpoints by setting in editor (click on Icon border) is working correct. The problem appears when user starts to modify the code (when some breakpoints are set already).
Putting several lines of code in place before set of breakpoints made that they are not updated in Breakpoints view, whilst in Icon border are correctly moved. And now, when debugging session has been started, breakpoints from Breakpoints view are used and application is stopped in wrong place.

It's easy to check if breakpoint are set correctly after modifying of code (adding lines). Just enough to click on every set breakpoint in Breakpoints view and compare where cursor is put in editor and where is breakpoint on Icon border.

This is refer to the project in C++ (using Qt). I didn't check other.

Reproducible: Always

Steps to Reproduce:
1. Open in KDevelop some bigger cpp file (several dozen of kilobytes).
2. Set couple of breakpoints (clicking in Icon border).
    For example 5 in places spaced apart with over a dozen lines.
3. Start debug session and after catching first one close this session, back to Code perspective.
4. Between first and second breakpoint put couple of line of code (copy -> paste, or just typing).
5. Compare Breakpoints view and breakpoints set in Icon border (simple recipe above).

Actual Results:  
In Breakpoints view all breakpoints placed after new code have wrong lines number (probably old ones).

Expected Results:  
Line numbers in Breakpoints view should match to all breakpoints set on Icon border (in editor).

I didn't check, but I suppose the same issue will happen in git version of KDevelop, because the most likely there is used the same code to managing breakpoints.