[fpc-devel] Debug Info proposal

Bogusław Brandys brandys at o2.pl
Sun Jan 13 18:36:58 CET 2008

Daniël Mantione wrote:
> Op Sun, 13 Jan 2008, schreef Joost van der Sluis:
>> Op zaterdag 12-01-2008 om 20:11 uur [tijdzone +0100], schreef Bogus?aw
>> Brandys:
>>> Jonas Maebe wrote:
>>>> You can already do this: compile a "release executable" with debug 
>>>> info,
>>>> and then distribute a stripped copy of that executable. The 
>>>> addresses in
>>>> the stripped executable will match exactly with the addresses in the
>>>> unstripped one.
>>>> Jonas_______________________________________________
>>> Wow! Great!
>>> Could fpc devel team provide application with source code which could
>>> translate addresses from bare bone stacktrace generated from stripped
>>> executable into full stacktrace with unit/line info using bare bone
>>> stacktrace file and executable with debug info included ?
>> Why would we? This is exactly what strip does! It strips out the
>> debug-info to a seperate file. This is wat the -debug package is when
>> you create a .rpm. That -debug package stores the debuginfo. If you
>> install the -debug package, you can use gdb to debug your application.
>> If you don't install it, you can't.
> To be honest, if you would receive a runtime error + stack backtrace 
> output from a user, converting it back to a source line back trace isn't 
> that easy currently. Sure, you can load the debuginfo executable in gdb, 
> then look up the lines one by one, but it would be a time consuming 
> process.
> Daniël


This is exactly what I mean.I need to be able to distribute stripped 
executable and yet be able to convert stacktrace provided by user to the 
source line info back again. I don't want the user to know where my 
program failed (unit name and line info).A tool doing this instantly 
could be appreciated.


More information about the fpc-devel mailing list