How do you use the debugger - gdb

[Elphi]

I've set some debugger options
type: gdb
path: /usr/bin/gdb

I've set compiler option to generate debug info for gdb.

I've set a breakpoint in my program.

When I run the program I expect that it stops at the breakpoint set, but it doesn't. What am I doing wrong?

[antonio]

My "Add BreakPoint" menu item is disabled. Is it enabled on your Lazarus?

[Marc]

@elphi: it the code run where you placed the breakpoint

@antonio: that dialog needs to be implemented, you can add a breakpoint by clicking in the left gutter.

[antonio]

Thanks.

[Elphi]

Sorry, I not familiar with gdb; where should hit code run? The run items in the IDE are disabled.
The breakpoint list show the breakpoint in state 'invalid'.

[Marc]

You see this invalid state while running, or before running ?

[Elphi]

Before running state = ? (On)
When running state = Invalid.

I've learned now that breakpoints set in the program body function as expected, but breakpoints in used units are somehow not recognized.
I also see that the first 30-40 steps after the breakpoint the "current-line" is set at strange places: at the method header, at empty lines, at defines that aren't valid etc. Can't say why it behaves as expected at some point.
Furthermore I get an access violation when I Reset Debugger.

When I run the program without breakpoints I can't figure out how to get the console I am supposed to see. Brings me to the original question: how to use gdb?

[Marc]

Pointing to wrong locations usually means that a different source is used for compiling than you use in the ide. (unless you're using some older 2.1.x compiler)

When a unit gets an invalid breakpoint, it can mean 2 things:
1) that unit isn't compiled with debug info. This is usually the case for rtl or fcl units. Only lazarus units are shipped with debug info.
2) that version of the unit is not used when compiling.

[Elphi]

Pointing to wrong locations usually means that a different source is used for compiling than you use in the ide. (unless you're using some older 2.1.x compiler)

Certainly not in this case. I've done a Clean Directory with default settings, and stepping through the source seems ok.

When a unit gets an invalid breakpoint, it can mean 2 things:
1) that unit isn't compiled with debug info. This is usually the case for rtl or fcl units. Only lazarus units are shipped with debug info.

Not the case here; it concerms my own units.

2) that version of the unit is not used when compiling.

The be sure I've the correct version of the unit I deliberately made a compile time error at the breakpoint line, and the compiler recognizes this error.

[Marc]

what fpc version do you use
what os (32 or 64 bit)
what debugger options did you set ?

[Elphi]

Lazarus 0.9.23 svn rev 12157, fpc 2.2.0 x86_64-linux-gtk on CentOS 5
Debugger type: gdb, path: usr/bin/gdb

[Elphi]

Lazarus 0.9.23 svn rev 12157, fpc 2.2.0 x86_64-linux-gtk on CentOS 5
Debugger type: gdb, path: usr/bin/gdb

[Marc]

with options I mean: project - compiler options - linking

[Elphi]

-g -gl

[Elphi]

Related to this bug report?
http://www.freepascal.org/mantis/view.php?id=9821[/url]