If Breakpoints step step into etc does work in Laarus it works
intermittently according to my eperience.
I dont use it anymore as it is not remotely similar in performance to
Delphi.
I debug by copying the program over and insert extis and cod to print
out variable and memory dumps before the steps where I get problems and
then move this code down like a breakpoint in order to evaluate where
the trouble in my code is.
Allthough this takes about 20x longer than Delphi's debuger, it does
solve the problem for me, but it is truly inefficient.
It would be really nice if Lazarus can have a fast and efficient "means
business" debugger that responds in a predictable way at least.
So far breakpoints take forever to be reached and the more complex a
program becomes the stranger the behavior.
This is not a rant, i just describe my experience and hope it would help
to make someone look at the debugger as the single most important
lacking feature of Lazarus. i understand that it might work for some
people, but I believe that is due to the fact that programs are simple.
The more complex, the more confusing the debugger behaves.
The program copied over to an old version of Kylix debugs really great
on Kylix. But, kylix is no more.
Joost van der Sluis wrote:
Okay, the problem was the stupid user behind the keyboard!! Every time
I upgraded to one of the unstable builds, I forgot to actually set the
debugger in Environment -> Debugger Options.
Sorry for the false alarm.
I make this mistake also now and then. Maybe it is an idea to generate a
warning, messagebox or something like that if a user has breakpoints in
his project and runs the program, but hasn't defined a debugger? Like:
"The project has breakpoints defined, but there is no debugger defined
in the environment options? The program is will be started without the
debugger."
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
