Debuging stops at unmarked Breakpoint

Hi, I have a trouble to use the debugging breakpoint. When I turned on the brakpoints, the model stops at a point that I didn't mark or check.
I tried many ways to get rid of the unexpected stop by doing
turning on and off all breakpoints,
recompile,
close and reopen model,
move around the breakpoints,
adding additional logic or comment line,
rename and save the model,
etc. etc. etc.

I couldnt get rid of the stops! Only way I can avoid the nuisance stop is turning off all of the debugging breakpoints.
Does anybody have the same experience?
Is it an indication of file corrupted or something?
Does it something to do with my logic??

The model runs well, though.
Please help me to get rid of the stop.

Thanks,
Sung

Did you try Build-> BuildFlexscript from the main menu?
Can you see the code path in the listed breakpoints? If so you can highlight it and press the delete key to remove it.

Hi, Jason,
Thank you for your suggestion and comment!
Yes, I tried Build>BuildFlexscript many times (Before/after save/compile/close). It doesnt help, though.

I am not sure your second suggestion. I do see the code path for the break points I intentionally "marked" in the breakpoints window. I don't see the code path of the annoying ghost breakpoint that model stops at. If I see it, yes you are right, I might be able to disable it or uncheck or delete it. Is it what you want me to check? Or, is it something else I can see when I build Felxscript??

I even tried to mark the point (making red dot, even though it is not the point I want to stop) and uncheck it in the breakpoints window. It doesnt work. It is just wired to me that it wouldnt go away.

Here is an interesting finding, though.
The annoying stop point is at the point AFTER a logic block that has several nested IF blocks. If I commented out nested IF blocks (replacing a dummy assign statment because no empty block allowed for IF) up to the top IF statement, it goes away.
I seems like the ghost breakpoint has something to do with my logic??
If I put the nested IF logic back, no matter what, the model wants to stop after the logic, even though I didnt mark or make it stop.

(Sigh..)

This is a known issue, and it's on the development list. It comes up so seldom and it's hard to reproduce. Is there any chance you could post your code that causes the problem?

Hi, Alex!

Thank you for your note!! Attached is the copy of my code. Apology for not uploading my entire model. I added some comments to explain what it does, but it is a basic "loop and if" logic to determine the exceptional dock door assignment using global table. As you see, I also use global macro values, add/delete/sort table command. I hope I didn't misuse or abuse the commands. Thank you again for your answer. I hope it helps to find out the cause.

Just an idea, but maybe it's usefull:

Have you checked the node MAIN:/project/model/Tools/Breakpoints ? If you haven't set any breakpoints this node should be empty.

Maybe there's something strange in this node that causes the problem

Hi, Carsten,
Thank you for the suggestion and idea.
Yes, I checked the treenode as you suggested, and no node for the nuisance ghost stop (Basically the nodes match to the Debug/Breakpoints menu window profile), but model still stops at the point that is not in the treenode, Breakpoints profile, or unmarked as red dot.

I know, it might not be a huge issue, but once it happens it could be very much annoying for the debugging.

Like Alex pointed out, I learned it was a known issue and Flexsim tries to find out what is going on. Until then, we could probably help them by reporting any same/similar experience, idea, or suggestion, as you do.

Thanks, again, Carsten.

Sung Kim,

You should send your model to support so that we can take a look at it to figure out why this issue is happening.