Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 572
    • Issues 572
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 111
    • Merge requests 111
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #104
Closed
Open
Issue created Feb 23, 2018 by Vicky Risk@vickyDeveloper

[RT#43640] Tool to gather all necessary files to accompany a core dump

When customers or others report a crash to us, they often don't understand what we need to be able to analyze the coredump file.

Evan said 'it would be cool to be able to run a tool that collects all the necessary file and tars them up ready to be submitted'.

Such a tool would need to be able to identify the binary from the core dump (or, optionally be told which is is), run ldd against the binary, collect all the libs, collect the debug symbols/package if these are separate and so on.

(There may be some contributed scripts around that are more generic we could use as the basis for this?)

Assignee
Assign to
Time tracking