https://bugs.kde.org/show_bug.cgi?id=362485
JATothrim <jarmo.tii...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |jarmo.tii...@gmail.com
Status|REPORTED |CONFIRMED
--- Comment #4 from JATothrim <jarmo.tii...@gmail.com> ---
This bug should be confirmed.
Effects are:
- Document breakpoint markers vanish, but the breakpoint still appears in the
list.
- Breakpoints may get deleted by document reload.
- Possible crash, if edited but not saved document is reload in debug session.
- Set breakpoint condition vanishes on reload.
Not caused by this bug:
- Breakpoint markers "jump" when saving document or toggling a breakpoint.
My analysis:
On document reload, KTextEditor component triggers
BreakpointModel::markChanged() in kdevelop that eventually calls into
BreakpointModel::updateMarks(). This cascades into even more markChanged()
events during reload that only make the effect worse.
markChanged() removes and re-adds breakpoints.
All this happens on document reload. The breakpoints you see afterwards may not
be the same instances, the original breakpoints are lost along with their
condition and ignore hits.
The faulty, or rather entirely missing handling of reload is isolated to
BreakpointModel. The used debugger backend should not matter.
I have nick named this bug as "marker cascade" :)
--
You are receiving this mail because:
You are watching all bug changes.
