Skip to content

lldb: coredump should resolve loaded modules via debuginfod #156305

@aag-norbert-lange

Description

@aag-norbert-lange

Hello,

I would like to open a coredump from a different system, and then lldb should be able to fetch the executable + debuginfo for all relevant libraries.

So what should be done:

  • get executable + debuginfo for process executable via debuginfod
  • get loaded modules in a similar fashion
  • get commandline arguments from coredump

What happens:

  • lldb seems to only load debuginfo, but not not map the executable memory
  • lldb tries to find the opened modules on the host. means it either finds nothing, or worse - map a wrong binary + debuginfo
  • this seems to be missing?

GDB works correctly and displays the commandline of the process too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions