A conditional breakpoint caused a good head scratcher today.
The before picture looks reasonable. The conditional breakpoint will stop execution when the parameterName variable equals some value.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjanbS-XAHSlDF2-bHBz2gp8wDvMnModvzlj8EiHKUfxL9xnfNzD-LomwO5ksxIriAmblpYZDT-FDWstm-h8Qc3Q2hFCd2yTdT8sZk8XMQNyAUcmsCCEM7oYK1X5oWEmqg0TPJyIB89CQhA/s400/BeforeConditionalBreakpoint.png)
The after picture however shows the simple but disastrous mistake.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEggaB7Z9RgZtvFKYwP2OttcHPA_VkXS87XlAkZdb34QHgDxLQOGb6yQNjHRf65MHZOeskT_iJQqKeeWX7JeLilSuUDnOjuVBd66sFqaoKIYkO03AQE1qOGuiBT6UwCGj0JTAfCNzlxJGF5T/s400/AtConditionalBreakpoint.png)
The conditional breakpoint is capable of assignment (which evaluates to false). So it will happily and transparently (unless you are looking closely) change the parameterName during execution.