[fpc-devel] Status of debug line info

Jonas Maebe jonas.maebe at elis.ugent.be
Tue Jun 23 16:15:25 CEST 2015

Sergio Flores wrote on Tue, 23 Jun 2015:

> The problem with gathering just addresses is that they change with every
> build (and I ship daily builds).

That's what -Xg is for (and on iOS/OS X, also the embedded UUIDs), so  
you can keep the debug info along with the build that you shipped out.

> Anyway I could try that, but I still need the base address, and I have no
> clue how to obtain that in FPC.

That's unrelated to the compiler or programming language, and specific  
to the OS. Your best bet is to look into the code of existing crash  
reporter frameworks.

> Could the compiler generate a internal table/array that mapped all
> functions addresses to strings?

Yes, but since it would just duplicate part of the debug information  
in another format, I don't think it would be worth it.


More information about the fpc-devel mailing list