Hi all,

I am using an unstable fpc version(2.1.1 -- snapshot from last week). While debugging my specific project, GDB(6.4 - Debian Sarge) seems to be wrong about the function locations so I cannot use breakpoints. I'd guess that this is a fpc bug about generated debug symbols. Is this is a known-unhandled issue or am I possibly doing something wrong?

Thanks,
Utku.

m utku wrote

I am using an unstable fpc version(2.1.1 -- snapshot from last week). While debugging my specific project, GDB(6.4 - Debian Sarge) seems to be wrong about the function locations so I cannot use breakpoints.

Do line numbers work?

I'd guess that this is a fpc bug about generated debug symbols. Is this is a known-unhandled issue or am I possibly doing something wrong?

No, it's not known.

Jonas

Jonas Maebe wrote
in

Yes, indeed I can use dump_stack without problems but still no luck with breakpoints. I can always reproduce this case:

(1) declare a test function like:
procedure foobar;
begin
// some code to avoid smart link elimination, just in case.
end;

(2) when I set a breakpoint in gdb, the filename and line of this breakpoint points to a wrong unit and lineno.

(3) interestingly, the map file generated by the linker doesn't even contain the foobar entry. (no optimization commands passed to compiler so it shouldn't be eliminated.)

ps. currently I was cross-linking from Windows, I will try a native build next...

Regards,
Utku.

Smartlinking happens depending on whether or not the procedure is reachable from the entry point of the program, not depending on whether or not it contains code.

(2) when I set a breakpoint in gdb, the filename and line of this breakpoint points to a wrong unit and lineno.

How do you try to set the breakpoint? You can either use: a) b FOOBAR
b) b sourcefile.pas:linenr

I guess you are using a) (of course that should work as well)

(3) interestingly, the map file generated by the linker doesn't even contain the foobar entry. (no optimization commands passed to compiler so it shouldn't be eliminated.)

Your default configuration file may contain -CX -XX. Alternatively, you may be looking for the wrong symbol name. It will be called something like P$PROGRAM_FOOBAR

Jonas

Jonas Maebe wrote
in

Another interesting thing is that I can set this with "b foobar" not "b FOOBAR". AFAICR documents were telling the reverse.

And also even if I set the breakpoint succesully with "b foobar", it will never trigger.

Your default configuration file may contain -CX -XX. Alternatively, you may be looking for the wrong symbol name. It will be called something like P$PROGRAM_FOOBAR

Nope, no smartlinking and no "foobar" text in the map file FYI.