BDebugger - not stopping execution on a breakpoint

[MGibs]

I've seen this happen before but haven't been able to reliably recreate the failure.

I don't believe it's ever happened for breakpoints I set directly in the debugger. I believe (could be wrong) that it has something to do with re-loading breakpoints that are saved to a file.

It just happened with a trivial file I was using for testing. In this case the code kept looping in the Do Forever loop without stopping on line 7 even though a Breakpoint was displayed there. I then looked at the Breakpoints tab and saw that there appeared to be a stray character (which I did not enter) in the condition column for this breakpoint. That's apparently why it wasn't stopping execution there. I will continue to see if I can find a way to reliably recreate the issue, but reporting here in case anyone else sees this happen.

 

[MGibs]

OK, well I do have some more info which might lead to recreating this issue.
My test .BTM and .BP file is reliably causing the issue.

When I start BDebugger with the line

bdebugger c:\yourpath\TestBDebugger.btm

the breakpoint looks fine in the Breakpoints tab.

As soon as I hit the Start button, the errant breakpoint condition shows up.

@rconn attaching the files so you can see if they cause the failcase for you.

 

[MGibs]

Here's a failcase starting with just the .BTM file I attached above.

1. Delete TestDebugger.btm.bp file (if it exists)
2. Start the Debugger (bdebugger c:\yourpath\TestBDebugger.btm)
3. Add a breakpoint to Line 7
4. Start a debugging session
5. Click run to breakpoint twice (Not once; must be twice)
6. Stop the debugging session
7. Close the debugger
8. Start the Debugger again (bdebugger c:\yourpath\TestBDebugger.btm)
9. Start a debugging session
10. The errant condition for the breakpoint reappears and Bob's your uncle.

 

[rconn]

Fixed in the next build.

The *.bp file is UTF-16 (to support Unicode chars in the Condition field). Windows failed to recognize it as UTF-16 so it was opened as ASCII and things went badly. This used to work; apparently Windows got pickier about recognizing Unicode files at some point (or Windows got broken).