[Lazarus] invisible break points??

[David Emerson]

Pew (piffle.the.cat) wrote:

> let's actually try helping the OP, Martin.
Hey, that's not necessary, man; Martin is very helpful, and I have solved the 
problem -- or at least I have a very effective workaround -- thanks to his 
troubleshooting. In fact I think I'm going to post it as a note to that console 
output mantis bug.

> Martin, please post the procedure up to the point where the code stops. 
> And under the list where it stops paste the error message from the View 
> / Messages window and some "^^^^^^^" to point to the code. That will help.
> 
> Also, try to set a breakpoint one line BEFORE where you have the 
> breakpoint set, as I believe that this is most likely the line where you 
> code is crashing. The press F7 to step into the code and see what is 
> going on. That way you will be able to watch what is really going on.

This is all utterly irrelevant.

> Good luck and happy debugging. All of this talk about how the debugger 
> works is not helping Martin, who only has one breakpoint set.

Yes it is. The problem is that the debugger is not working properly!!

The solution is to redirect the program's writeln output, via the Run Parameters 
dialog. Using a simple posix-style redirect:  >writeln.log

Cheers,
David