according to the man page (man perldebug), this is proper behavior, however i'm sure it would be possible to override this behavior in the code.
i've been using the debugger a bit more and have noticed some annoyances (and bugs), so i'm going to try and start looking at that code after i finish up w/ the clickable breakpoints.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
the debugger always stops at the first command, even if there is no breakpoint.
Is this behaviour wanted?
Thanks
I don't like this behaviour either. However, the debugger code is messy, so it seems difficult to fix.
Hmmm... I'll try to look at the code. But I am neither a java-guru nor I have much time.
according to the man page (man perldebug), this is proper behavior, however i'm sure it would be possible to override this behavior in the code.
i've been using the debugger a bit more and have noticed some annoyances (and bugs), so i'm going to try and start looking at that code after i finish up w/ the clickable breakpoints.