Anyone else having these problems just simply using the LS debugger with a Notes client with 8.5.1:
=> Frequent crashes when turned on
=> Periodically refusing to allow the designer to assign a breakpoint while a script is running
=> Frequently hides the sub/function name in the event window
These misbehaviors seem to occur most frequently within a sub or function called by another form element.
It’s frustrating beyond belief, and I don’t understand how IBM could have gotten it this wrong. The debugger is failing/crashing with plain old subs and functions in the form itself - not even stored in script libraries or agents.
Surely my work group isn’t the only part of the Domino developer community having these issues - yet I see none of them addressed in any of the existant or planned Fix Lists for 8.5.1 or 8.5.2. IBM, what gives?
I’m a bit late to post a reply but obviously just had a similar moment to the one you had when you posted! This is in 8.5.2 so no improvement.
This is an example: start debugging a script, hit a breakpoint which was set previously, set another breakpoint, hit the second breakpoint which now no longer has the red circle next to it, and now I can no longer set, unset or disable any breakpoints, except for sometimes you can set a breakpoint but you can’t see that it’s been set and you certainly can’t remove it, and nothing showing in the Breakpoints tab, not even your original breakpoint (all reproducable, except the bit about being able to set breakpoints sometimes - that’s intermittent). Especially annoying if the one you now want to unset is in the middle of a loop.
The only way to get around it is to stop your script and relaunch at which point any or none of your previously set breakpoints may have persisted.
The lotusscript debugger has always been a bit flaky but it does seem to be worse than it used to be for reliably being able to manipulate breakpoints. I guess lotusscript is on the back burner a bit these days though.
Subject: Re: This is reproducible? Have you opened a PMR?
That sounds like a good idea but I don’t believe that I have a way of doing this. Now that Domino Designer is freely downloadable by anyone, is there any way of submitting PMRs without having an IBM customer ID?
I don’t expect free software to be supported, but it seems like it would make sense for there to be a way of easily reporting reproducable issues like this.
Interestingly, this particular instance seems to be confined to a particular function within a particular script library. Other functions in the script library work fine, but a new agent set up to run the same function has the same problem.
Also, copying the function and giving it a new name doesn’t fix it so there must either be something in my specific code causing the problem, or it’s to do with where the breakpoints are placed in terms of nested loops, If statements, etc.
I’ve definitely seen this problem with other scripts, although I haven’t taken the time to look into it before, so I’m inclined to believe it’s to do with relative placement (first breakpoint well within the nested statements, second breakpoint out in first loop, or something like that). Having said that, I sort of like the idea that my code style has the power to bring down the debugger
I completely forgot to get back to you about this. I can’t reproduce this problem here, but I may be able to help anyway. Breakpoints are stored in profile docs, according to what I’ve learned, but I don’t know exactly where. Can you examine the DB, your bookmarks DB, and perhaps your workspace for profile docs? If you find one that you know shouldn’t be there you can probably delete it and completely restart Notes and your problem will probably be gone.
