Shipping core libraries with debug symbols

[Simon Marlow]

I've been building the RTS with debug symbols for our internal GHC build 
at FB, because it makes investigating problems a lot easier.  I should 
probably upstream this patch.

Shipping libraries with debug symbols should be fine, as long as they 
can be stripped - Peter, does stripping remove everything that -g creates?

Cheers,
Simon

On 02/01/2015 23:18, Johan Tibell wrote:
> Hi!
>
> We are now able to generate DWARF debug info, by passing -g to GHC. This
> will allow for better debugging (e.g. using GDB) and profiling (e.g.
> using Linux perf events). To make this feature more user accessible we
> need to ship debug info for the core libraries (and perhaps the RTS).
> The reason we need to ship debug info is that it's difficult, or
> impossible in the case of base, for the user to rebuild these
> libraries.The question is, how do we do this well? I don't think our
> "way" solution works very well. It causes us to recompile too much and
> GHC doesn't know which "ways" have been built or not.
>
> I believe other compilers, e.g. GCC, ship debug symbols in separate
> files (https://packages.debian.org/sid/libc-dbg) that e.g. GDB can then
> look up.
>
> -- Johan
>
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>