Skip to content

How to handle (native) debug info? #267

@omajid

Description

@omajid

In the context of packaging for various Linux distributions, the topic of (native) debuginfo comes up.

Here is what many linux distributions do:

  1. Build a package with full debuginfo (-g with gcc/clang, RelWithDebInfo for cmake)
  2. Run a separate tool to find all debuginfo, strip it and move it to a separate package (-debuginfo for Fedora/RHEL/CentOS, -dbgsym for Debian/Ubuntu).

Now if users want to just run .NET Core, they install dotnet. If they want to use the debug symbols, they need to install dotnet-debuginfo or dotnet-dbgsym (or the variant used by the distro).

Neither source-build nor the current official build accounts for this. These builds just strip out everything that leaves the package build process nothing to work with. For example, see https://github.com/dotnet/core-setup/issues/1607

I would like to "fix" this in source-build. Should I just remove the various invocations to strip debug info? Is there a need to make this conditional depending on the current platform? Or even build type?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions