Problem with stability breakpoints

[MadJim]

Good day!

I could not find something similar on my problem here in the forum, sorry if this has already been discussed.

I have been actively used in developing the set of breakpoints, marking all interesting places in the code package to the performance not miss the opportunity to fine-tune feature of their behavior. Some points can stop long enough to remain active until I get to them.
But with this approach to the development and debugging are often faced with a situation of spontaneous displacement of the installation site that points back and forth, causing them completely useless and loss of important places mentioned paying attention.
Long been trying to understand what my actions lead to these chaotic shifts, but I do not find an answer.
Please help me solve this problem.
Thank you!

PL / SQL Developer Version 10.0.5.1710

 

[Marco Kalter]

I'm not quite sure what you mean. Can you provide an example?

 

[Sgnao]

I think I understood what you mean.

When you set breakpoints on Program Windows it's positional and if you add or delete lines (or simply beautify the code) before the breakpoint it won't shift, but it stays on the line you originally put it.

Obviously there's no workaround, but I can advice you to put breakpoints directly on test window when debugging.

That's how I do it, when in need of.

Hope this helps.

Marco

 

[MadJim]

Thanks,
but you described a very simple example of the shift breakpoint, which occurs in the visible part of the editing window, so noticed and corrected me immediately.
I'm having a bit more difficult situation.

 

[MadJim]

And about the council set the debug point in the test window: often when debugging I can not remember where and what has been fixed, and does not always start debug begins with the desired method to me and get to the depths of the logic and then mark the appropriate place - not acceptable for me.

 

[MadJim]

Ok, I will describe step by step:
1. open a separate program window with package
2. make changes and marks important for me line of code by breakpoints
3. open a separate test window for debugging one of the package methods
4. in process of debugging i find a place to fix the code and immediately without closing the debug session, or previously ending debugging and closing the test window, go back to make changes to the program window

Next are several times, repeat steps 3 and 4.

5. Returning once again to the source code in the program window, somewhere i find offset breakpoints.

I have suggested that some operation of changing code when you insert or delete rows of corresponding package does not offset the breakpoints that continue to point to the preceding provisions of lines of code.

 

[MadJim]

I found moment offset breakpoints!
1. Set the points in the program window
2. Run the test window, debugged process. Certain points in the process removed
3. When you have finished debugging, back into the program window and remove the three commented lines (-- ...) in one place and not far from the first - two commented lines.
4. ??? Then, supposedly, compiled package (often do this automatically without noticing)
5. Scroll down the text of the package in the same window and found exactly offset set points down five lines, ie, the text was reduced to five lines and shifted, and remained at the same points, the old line number. Breakpoints is above the modified space is left on the right places.

Can you repeat that scenario and to confirm or deny?

 

[MadJim]

Some kind jumping bug.
Specially repeated scenario again on another part of the code - all breakpoints remained in their places.

 

[shangjing]

Looking forward to a better answer！

 

[MadJim]

Analysis and correction of errors, apparently, you do not have a priority.