[Lazarus] invisible break points??

[Martin]

On 06/01/2011 20:51, David Emerson wrote:
> I am having a very strange and frustrating experience with lazarus, in my fpGUI
> app.
>
> When running, after pressing a button in my app which calls a process, the app
> seems to freeze up. It just sits there, unresponsive. My program has no
> breakpoints in it.
You mean your app forks a new process (or executes another app as new 
process)?

> The only way I can get it to move is by *adding* a breakpoint, somewhere within
> the code that it is waiting to execute. Then it stops at that breakpoint. I can
> remove the breakpoint, tell it to run, and it continues on its merry way.
very strange...

> If my program *does* have breakpoints in it, it will not get to them. Lazarus
> seems to need to have a breakpoint *added* into the code, *during* the run,
> before it will proceed.
>
version of gdb?

You should at least attach the output of the "debug output" window (from 
"view" / "debug windows")

Also open the breakpoint window and check there is no other breakpoint 
(even so, if there was, and if it was hit, it should stop there)

Also start Lazarus from console, and watch for any output of the IDE. It 
may report something there....

32 or 64 bit? or maybe a mix? 64 bit system, but running 32bit apps?

Martin