[Lazarus] RE : RE : Generating line info

[Ludo Brands]

> Also see my other mail: dwarf will solve some of the issues that new 
> users (and old users too often complain abut). It does make 
> some (only 
> some, but at least that) of the properties inspectable.
> 

Our mails crossed eachother.

> I admit, the fact that people would include debug info for 
> the purpose 
> of stacktraces on stderr only (and not to use gdb), never 
> came to mind. Yet, even if there would not have been a 
> reason: except for the recent 
> bug in infodwrf (which hopefully will get fixed) I never 
> thought there 
> was an important difference for stacktraces. Of course, I have never 
> attempted to read them myself => I do use them (very 
> frequently) but I 
> always import them into "leak view", so I never realized the 
> difference.
> 

"Leak view" is using heaptrc to get the info. So you're bound to hit the
same bug and issues one day or another.

The other point that needs to be understood is that only the lineinfo or the
lnfdwrf unit is loaded, not both (pmodules.pas line 659) . That means that
ALL modules (LCL, RTL, external statically linked modules) need to be
compiled with the same debug info to get maximum use of heaptrc or crash
trace dumps. GDB uses all debug info available, including the coff symbols
that are still present in the windows dll's.

Ludo