Double click in left gutter to remove a breakpoint sometimes sets another on the same line
Lukas is seeing this bug, have not reproduced it yet. Creating a ticket nevertheless so that it's not forgotten.
We need to add some logging on breakpoint set actions so that the user can send us more information.
We need to add some logging on breakpoint set actions so that the user can send us more information.
Leave a comment
on 2011-03-25 09:11 *
By Iulian Dragos
Version set to 1.0.0-SNAPSHOT
Eclipse version set to Helios
Branch set to wip_experiment (2.9)
Updating tickets (#1000238, #1000326, #1000331, #1000264, #1000298, #1000314, #1000315, #1000325, #1000329, #1000333, #1000277, #1000209, #1000210, #1000288, #1000299, #1000300, #1000301, #1000305, #1000309, #1000310, #1000327, #1000270, #1000292, #1000293, #1000294, #1000295, #1000297, #1000303, #1000304, #1000312, #1000320)
on 2012-01-27 14:36 *
By skyluc
Type set to Enhancement
Version changed from 2.0.0-beta1 to 2.0.0-final-29
Eclipse version changed from Helios to All
Assigned to changed from Hubert Plociniczak to -none-
Component changed from None to Debugger
Milestone changed from Helium to Enhancements
Permission type changed from None to Public
I have seen this too.
It is likely due to a combinaison of adding a breakpoint in a closure, at runtime it gets linked to the closure type. Then adding or removing lines number so the old line position inside the closure.
It is likely due to a combinaison of adding a breakpoint in a closure, at runtime it gets linked to the closure type. Then adding or removing lines number so the old line position inside the closure.
on 2014-07-05 13:49 *
By Simon Schäfer
Version changed from 2.0.0-final-29 to 3.0.4-211
Status changed from New to Accepted