>>Hi,
>>
>>I am having trouble with the debugger and wondered if I have triggered some sort of setting some place or maybe the framework being used is doing something odd.
>>
>>If I set some breakpoints, they often do not get "respected" i.e. set a breakpoint for when a certain method fires and then I often want to either "run to cursor" or I mark a line way down in the code to stop again and then I resume so I don't have to step through everything.
>>
>>Somehow the breakpoints are not being respected and the entire method runs and finishes. If I look at the breakpoint dialog, they are still set but somehow the deugger is not stopping.
>
>The debugger does have some quirks, but what you describe is not one of them, at least in my experience.
>
>Every time I had the debugger consistently fail to stop where I expected it to, the reason was one of these:
>
>1) I had two similar places in code, set the breakpoint in one but ran the other
>2) I had a prg with twice the same procedure/method/function. The last one (i.e. the one last compiled) wins and gets run; if I put a breakpoint in the first one, it won't fire.
>3) I had a condition, a scan-for, do while, if or case block with a breakpoint in it, which I thought must fire. Well, if it didn't, that's because the condition that I was convinced must be true turned out to be false - so in such cases I put the breakpoint before the block. So
>3.1) if it doesn't enter the block, I examine the condition and the values it is comparing and see what's different from what I thought it would be
>3.2) if it does enter the block and then still doesn't reach your code, well, there's another instance of 3) inside the block. Since you're already in the debugger, set a temporary breakpoint where you suspect the code doesn't do what you expect.

Dragan,

what he describes occurs if you have many layers of classes and large callstack on it.

You doubleclick in the debugger
- no breakpoint mark (visibly) set, breakpoint not respected
- breakpoint mark set, breakpoint not respected
- run-to-line (F7) fails

it runs through the line.

I have this on a regular base.