On 07/01/2011 12:25, José Mejuto wrote:
Ah! another hint, in that cases the breakpoint does not change to
invalid breakpoint when run.
See my other mail. It is not as easy as it sounds.
If there are only one or 2 breakpoints, the time to load the line info
for those units can be tolerated. If there are many, and the IDE tries
to load all those line infos then people will start complaining that it
takes forever to start-up/run a project in the debugger.
But that's not even the reason. Breakpoints can be in libraries, which
are not yet loaded. In that case they can not be disabled or you
breakpoints would stop to work for libraries... And that sure would
cause some complaints.
Yes it would be possible to work around that (the library issue) too.
But at some cost....
As I said, it is easy to check your breakpoints via the breakpoint list
window...
Imho the most reasonable course of action is to check at the time the
breakpoint is hit.
So if the IDE stops at a breakpoint, it should check that the breakpoint
actually is at the same place that the debugger stopped.
If not it should present the user with a set of reasonable options:
ignore, remove, disable or relocate breakpoint....
BTW, I never knew this was an issue, I encountered that many times
myself, it never did bother me at all. Until this mails I never saw any
complaint (at least none that I could relate to this issue)..,
Martin
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
