Traditionally, setting a data breakpoint in a debugger for an execution environment that uses compacting garbage collection is ineffective as a compacting garbage collector moves data around in memory as part of its compaction process. Traditional debugging approaches such as tracing each insertion, etc. are impractical because of the quantity of operations encountered in a typical program. Described herein is a data breakpoint for a compacting garbage collection environment in which data breakpoints are disabled while the garbage collector is running, creating notifications for move operations, batching the notifications, retargeting data breakpoints and using the batched notifications to re-enable the disabled breakpoints.