Why can't some code lines be breakpointed?

[WSinc]

In a subroutine I was working on, I had a CALL statement as the last line before the END statement.

When I tried to set the breakpoint there, it skipped entirely down to another subroutine in the same source

cose file. This was a subroutine that was only called from the one above it, and nowhere else.

Is there a way to insert a "Junk line" that CAN be breakpointed? X=X doesn't work, because the

compiler does not generate code for it. Maybe X=Y, where X and Y are junk variables?

Why would it not let me breakpoint the line I am interested in?

[DavidWhite]

a CONTINUE statement could work.

One possible cause of not being able to set a breakpoint is that the version of the source code you are viewingis out of date w.r.t. to the debug files. You could try rebuild all to check that this is not the case.

Regards,

David

[Steven_L_Intel1]

The symptom suggests that the EXE or DLL you're running/loading is not the one built in the project.

[WSinc]

Yes, but this happens right after I do a CLEAN and REBUILD.

So there is no OLD executable, I assume......

I noticed that when I put the breakpoint at a DO statement, it breakpoints after it's inside the loop.

I want it to breakpoint right before it starts the loop.

Is there a way to put in a JUNK line to be breakpointed?

[nvaneck]

I see this sometimes when I try to insert a breakpoint while debugging. Breakpoint appears out of place and doesn't seem to work until I restart. So sometimes I need to stop debugging, put in the breakpoint, and restart.

[Lorri_M_Intel]

RE: Is there a way to put in a JUNK line to be breakpointed?

You could try the CONTINUE statement (as suggested already :-) )

What version are you using? We had some line-correlation issues in 11.0.xx and earlier; this sounds like that.

- Lorri