Is there a known issue on Mac?

The following was observed on 2 different 32 bit Mac:

compiling from lazarus tests/lazutils/testunicode.lpi with -gs / also entire LCL compiled with -gs / standard fpc 2.4.4 installation (I would assume that does not have dwarf? but I do not know)

info line
"/Users/felipe/Programas/lazarus/test/lazutils/testunicode.pas":182

&"info line
\"/Users/felipe/Programas/lazarus/test/lazutils/testunicode.pas\":182\n" ~"Line 182 of \"testunicode.pas\" starts at address 0xedb and ends at 0xef6.\n"
^done

same address when trying to insert a breakpoint

-break-insert -f testunicode.pas:182
^done,bkpt={number="11",type="breakpoint",disp="keep",enabled="y",addr="0x00000edb",file="testunicode.pas",line="182",shlib="/Users/felipe/Programas/lazarus/test/lazutils/testunicode",times="0"},time={wallclock="0.00016",user="0.00016",system="0.00001",start="1318483988.064643",end="1318483988.064808"} (gdb)

running, pausing, and using the disassembler on the stackframe containing that code, shows addresses in the 0x011xxx range.

So it seems the symbols are not relocated?

It's not specific to FPC:

Breakpoint 1, 0x00001fdc in main () at tt.c:7
7 }
(gdb) info line 6
Line 6 of "tt.c" starts at address 0x1c and

Hello,

Then maybe the default debug info created by -g on Mac should be dwarf2? dwarf2 works correctly in my tests.

Is there a table somewhere about which debug info types are default in each operating system?

Felipe Monteiro de Carvalho wrote

Then maybe the default debug info created by -g on Mac should be dwarf2? dwarf2 works correctly in my tests.

Yes, I agree it's about time to change that (along with making - godwarfsets the default). It requires at least the latest gdb from Mac OS X 10.5 to work correctly, but that should be no problem anymore.

Is there a table somewhere about which debug info types are default in each operating system?

No, and such table will not be made because it's an implementation detail. If you require a particular debug information format, specify it. Anything else will break as soon as the default is changed from one compiler version to another.

Jonas

One downside is that -gl doesn't work with DWARF on Mac OS X though (because it's not implemented, and requires a completely different implementation compared to other platforms).

Jonas

But maybe a switch could be added, where an fpc exe gives feedback, what it currently defaults to?

If you depend on a particular debug format, set it. If you don't, then the compiler doesn't need extra code to tell you. Besides, what the debug format is for a particular file does not tell you anything about other code in the program anyway.

Jonas

In our previous episode, Martin said:

in the case of the multiple RTL situation, the target designation gets enhanced with the encoding (or at least 1byte/2byte, since it might be possible to switch a 1byte RTL to be either utf8 or ansi by changing the default codepage)

As the subject indicates, this thread is about the debug format. It is unrelated to strings.

Jonas