Bug 149301

Summary:	some kind of a "breakpoint flood" if you delete a block of code containing lines with breakpoints
Product:	[Applications] kdevelop	Reporter:	Dmitry <korvin>
Component:	CPP Debugger	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	3.4.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	5 screenshots showing the bug

Description Dmitry 2007-08-28 13:14:18 UTC

Version:           3.4.1 (using KDE 3.5.7, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.22-gentoo-r2

To reproduce the bug you need the following:

0) Put the breakpoint in some accessible point (such as main()) 
1) START THE PROGRAM under the debugger and wait until the breakpoint hits
3) For more effect add some breakpoints around that line, three or four would be enough.
4) Now start selecting the code from the middle of the 'red coloured' breakpointed code to some lines up or down.
5) hit the 'del' button and you get the thing! :) Depending on the count of erased lines you may get a real flood of breakpoints and even the program crash.

Comment 1 Dmitry 2007-08-28 13:24:27 UTC

Created attachment 21498 [details]
5 screenshots showing the bug

This is a slideshow (tbz2 arch with png's) describing the bug in the visible
form. 

P. S: Even if you try to undo the operation, breakpoints will stay (of course).

Comment 2 Andreas Pakulat 2007-08-28 15:07:13 UTC

This is actually a duplicate and the workaround is to not edit the code while the debugger is running.

*** This bug has been marked as a duplicate of 70815 ***

Comment 3 Dmitry 2007-08-28 20:13:39 UTC

Yes, of course, editing the source in the debug process is quite strange... maybe it is a good idea to put an option like "switch the editors to the read only mode while debugging"? I think it will be useful to prevent such things in future (sometimes it may be very annoing).