On Tue, May 5, 2009 at 1:06 PM, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Hi,
Why is Lazarus ignoring my breakpoint? If I put a writeln() statement
before line 1466, it is executed and I see console output. So that
I place the following writeln() statement before line 1466 and below
Hi,
Why is Lazarus ignoring my breakpoint? If I put a writeln() statement
before line 1466, it is executed and I see console output. So that
code is definitely being run. Yet Lazarus think it isn't and simply
ignores the breakpoint - for no reason. See attached screenshot.
I'm using FPC 2.2.5,
Graeme Geldenhuys schreef:
Hi,
Why is Lazarus ignoring my breakpoint? If I put a writeln() statement
before line 1466, it is executed and I see console output. So that
code is definitely being run. Yet Lazarus think it isn't and simply
ignores the breakpoint - for no reason. See attached
Graeme Geldenhuys wrote:
On Tue, May 5, 2009 at 1:06 PM, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Hi,
Why is Lazarus ignoring my breakpoint? If I put a writeln() statement
before line 1466, it is executed and I see console output. So that
I place the following writeln()
On Tue, May 5, 2009 at 1:33 PM, Martin Friebe laza...@mfriebe.de wrote:
While it is not the answer to your question, I had a similar issue and
found, that breakpoints only worked, if they here set *before* I started
the application to debug. (This was on FreeBSD)
This is what I have done. Set
On Tue, May 5, 2009 at 1:31 PM, Vincent Snijders
vincent.snijd...@gmail.com wrote:
The color of the breakpoint seems to indicate there is no line info for
With my color scheme in says: invalid breakpoint
that unit. Can you attach the debug output (maybe zipped) (View - Debug
Windows - Debug
Graeme Geldenhuys wrote:
On Tue, May 5, 2009 at 1:33 PM, Martin Friebe laza...@mfriebe.de wrote:
While it is not the answer to your question, I had a similar issue and
found, that breakpoints only worked, if they here set *before* I started
the application to debug. (This was on FreeBSD)
On Tue, May 5, 2009 at 2:28 PM, Marc Weustink wrote:
You cannot debug console apps with lazarus. If you use an xterm as
launching to see your console output, then gdb will debug the xterm and
not your app.
Ah, that was it!! I switched to using the LCL based GUI version of
the test suite and
Don't tested but, what about adding an Sleep at the start of the console
app, then attach lazarus to your console process?.
Leonardo M. Ramé
Griensu S.A. - Medical IT Córdoba
Tel.: 0351 - 4247979
Graeme Geldenhuys escribió:
On Tue, May 5, 2009 at 2:28 PM, Marc Weustink wrote:
You
Graeme Geldenhuys schreef:
On Tue, May 5, 2009 at 2:28 PM, Marc Weustink wrote:
You cannot debug console apps with lazarus. If you use an xterm as
launching to see your console output, then gdb will debug the xterm and
not your app.
Ah, that was it!! I switched to using the LCL based GUI
10 matches
Mail list logo
