ScottMattes
Member³
Can a 'run to cursor' option be done in debug? It would cut down on one time only breakpoints (adding, removing).
Thank you.
Thank you.
Enhancement Request: debugging
- Thread starter ScottMattes
- Start date
Claus Pedersen
Member³
+1 for this.
The PLD pseudo code for this feature should be quite simple to implement:
1. Clear (and remember) all breakpoints
2. Set a new breakpoint at the requested line
3. Run to breakpoint
4. Remove breakpoint
5. Restore all previous breakpoints
The PLD pseudo code for this feature should be quite simple to implement:
1. Clear (and remember) all breakpoints
2. Set a new breakpoint at the requested line
3. Run to breakpoint
4. Remove breakpoint
5. Restore all previous breakpoints
I have added this to the list of enhancement requests.
ScottMattes
Member³
Patrick,
Thank you for pointing this out.
That wrong click modify breakpoints is more suited (for me at least) for limiting how often the breakpoint stops execution (Use Pass Count) or when a certain condition is met.
I will have to look into using Use Message along with Don't Break as those might be very useful.
Thank you for pointing this out.
That wrong click modify breakpoints is more suited (for me at least) for limiting how often the breakpoint stops execution (Use Pass Count) or when a certain condition is met.
I will have to look into using Use Message along with Don't Break as those might be very useful.
ScottMattes
Member³
PLSD 10.0.5
Marco,
The help file, for Use Message under Breakpoint Conditions, says "and if the conditions are met, the message will be places on the output page'.
So, I put a breakpoint on a line in a package, started a test window on that unit and ran doing Step In until that line executed and execution was a few lines past the breakpoint, but I see no output on the DBMS_OUTPUT tab.
I ran another test, with two breakpoints, both set to give a message and this time I see the second message on the DBMS_OUTPUT tab, but not the first breakpoint's message.
I was trying this out because I wondered if messages could contain variable values, and it appears that we cannot include variables (like, if the message entered was 'loopcnt=:loopcnt' I'd like to see 'found loopcnt=1'
Marco,
The help file, for Use Message under Breakpoint Conditions, says "and if the conditions are met, the message will be places on the output page'.
So, I put a breakpoint on a line in a package, started a test window on that unit and ran doing Step In until that line executed and execution was a few lines past the breakpoint, but I see no output on the DBMS_OUTPUT tab.
I ran another test, with two breakpoints, both set to give a message and this time I see the second message on the DBMS_OUTPUT tab, but not the first breakpoint's message.
I was trying this out because I wondered if messages could contain variable values, and it appears that we cannot include variables (like, if the message entered was 'loopcnt=:loopcnt' I'd like to see 'found loopcnt=1'
Last edited:
Similar threads
- Discussion
