[Lazarus] invisible break points??

[David Emerson]

Martin wrote:
> Hm, I guess part of the problem is that console output of the 
> application does not work well with gdb. It seems to mix with the gdb 
> output....
> 
> the msgs from gdb goes on the same line, as the app's output.
> There is nothing the IDE can do, it has no chance of  identifying the 
> gdb output, or knowing there was a breakpoint...

yeah. next time I test this I'll see if I can suppress output.

> see http://bugs.freepascal.org/view.php?id=12172
> I haven't looked at this issue further, not sure if there are updates or 
> when there will be. (I know not the news anyone wants to hear; but it 
> seems it's a bug that will take a while to fix / we are unfortunately 
> bound to gdb, there isn't any better solution yet)

I did try the run parameter: >logfile
...a basic redirect. And it worked! program output was redirected to the file, 
and gdb info was seen in the debug output window. Unfortunately, the buffer 
doesn't get flushed until the program exits, so the usefulness is limited, but 
certainly better than none, as I had before.

Then I tried to make it a named pipe: mkfifo logfile. The program stalls until 
something is listening at the other end of the pipe. So "cat logfile" on my 
terminal allowed the program to continue executing. Unfortunately, the output 
doesn't come in real time-- even with the named pipe, it seems only to flush 
after the program exits normally. In fact, if I use ctrl-f2 in lazarus to 
abort, the buffer is never flushed, and "cat logfile" exits with no output 
(except I guess an EOF I don't see)

> IIRC you are using a very recent Lazarus
0.9.29-0-20101231

> > So at this point, I put the same breakpoint back in. The gdb window shows:
> 
> Have you tried, if you can F9 after that, and continue?

yes, once I remove the breakpoint and put it back in, the program functions more 
or less normally.

> the symlinked files may come from old lpi/lps files ... either in 
> project file or in ~/.lazarus/projectsessions
> the IDE did have issues creating some invalid pathes, but the ones I 
> knew of have been fixed (but pathes in lpi/lps would remain)

I created a fresh project, and got rid of some old cruft. So we'll see if things 
work more smoothly from here on out.

As for the breakpoint error, even creating the new project file did not 
eliminate the problem. After that, I fudged around a bit deleting files here 
and there, and the problem eventually disappeared. I'll have to get my 
brother's files again in order to re

> Well it is already on mantis.....
the symlink bug or the breakpoint problem?


Thanks so much, Martin
~David.