Inexplicable breakpoint behaviour
Good morning, i have noticed some odd breakpoint behaviour in my code. Typically when i get unresolvable breakpoints in conditional statements its a type or logic error (my own fault). However in this case the logic is trivial. In the first picture, with a _nop() following the else() i can place the breakpoint as shown. However if i remove the _nop() and recompile i get a broken breakpoint and a note that it cannot be resolved to a memory address.
Has anyone seen behaviour like this before?