Set step on is the only way to avoid this behavior. As I said, it only breaks at this ghost break point when I have another break point set. I try to avoid using set step on for a number of reasons.

>You by chance don't have the statement:
>
>

>SET STEP ON
>

>
>In the code -- this is an explicit call to the debugger.