[Bug tools/27573] New: eu-unstrip: assemble debugable executable for a core file

[Bug tools/27573] New: eu-unstrip: assemble debugable executable for a core file

[mliska at suse dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

            Bug ID: 27573
           Summary: eu-unstrip: assemble debugable executable for a core
                    file
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tools
          Assignee: unassigned at sourceware dot org
          Reporter: mliska at suse dot cz
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Having a core file, it would be handy to assemble a debugable executable with
debuginfod client. I mean downloading both executables/shared libs and
corresponding debug info for these modules:

Example:
$ eu-unstrip -n --core 12sp3-sssd.core.715
0x400000+0x213000 41b05d41005e68f89b5422f1683b26c332f2d2e6@0x400264 - -
/usr/sbin/sssd
...
$ ls -l /usr/sbin/sssd
ls: cannot access '/usr/sbin/sssd': No such file or directory
$ debuginfod-find executable 41b05d41005e68f89b5422f1683b26c332f2d2e6
/home/marxin/.cache/debuginfod_client/41b05d41005e68f89b5422f1683b26c332f2d2e6/executable
$ debuginfod-find debuginfo 41b05d41005e68f89b5422f1683b26c332f2d2e6
/home/marxin/.cache/debuginfod_client/41b05d41005e68f89b5422f1683b26c332f2d2e6/debuginfo

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I assume this would be some kind of "pack" command? Which would pack all
relevant files, executables and debuginfo together into one directory?

Maybe it should be an extension to debuginfod-find.
Something like debuginfod-find pack <corefile> <dir>?
Should it just be the executable? Include the debuginfo? Sources?

Could you describe the use case a little more?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[mliska at suse dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #2 from Martin Liska <mliska at suse dot cz> ---
(In reply to Mark Wielaard from comment #1)
> I assume this would be some kind of "pack" command? Which would pack all
> relevant files, executables and debuginfo together into one directory?

Exactly.

> 
> Maybe it should be an extension to debuginfod-find.
> Something like debuginfod-find pack <corefile> <dir>?
> Should it just be the executable? Include the debuginfo? Sources?

It should be likely something that can gdb properly consume.

> 
> Could you describe the use case a little more?

Imagine you receive a core file for an old supported product. You want to
investigate it in gdb on a different machine (with a more recent OS) and you
want to get all the needed debugging information from a debuginfod server.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
A single coredump executable that contains all the solib bits + all the
debuginfo for all the solibs ... is that even possible in principle?

If the use case is letting a gdb user without debuginfod connectivity of her
own access a cache of debug content ... perhaps transmit a tarball of
$HOME/.cache/debuginfod along with the core dump?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #4 from Frank Ch. Eigler <fche at redhat dot com> ---
see also  perf-archive(1)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[mliska at suse dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #5 from Martin Liska <mliska at suse dot cz> ---
> If the use case is letting a gdb user without debuginfod connectivity of her
> own access a cache of debug content ... perhaps transmit a tarball of
> $HOME/.cache/debuginfod along with the core dump?

That can be a solution. To be honest, gdb should be able to load all these with
libdebuginfod-client library.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #6 from Frank Ch. Eigler <fche at redhat dot com> ---
> To be honest, gdb should be able to load all these with libdebuginfod-client library.

It can - as long as $DEBUGINFOD_URLS is set to something, anything, the client
library will gladly check out the cache.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[mliska at suse dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

Martin Liska <mliska at suse dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://sourceware.org/bugz
                   |                            |illa/show_bug.cgi?id=27570

--- Comment #7 from Martin Liska <mliska at suse dot cz> ---
(In reply to Frank Ch. Eigler from comment #6)
> > To be honest, gdb should be able to load all these with libdebuginfod-client library.
> 
> It can - as long as $DEBUGINFOD_URLS is set to something, anything, the
> client library will gladly check out the cache.

Apparently, the support is somehow missing:
https://sourceware.org/bugzilla/show_bug.cgi?id=27570

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/27573] eu-unstrip: assemble debugable executable for a core file

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27573

--- Comment #8 from Frank Ch. Eigler <fche at redhat dot com> ---
OK - once gdb fixes that shortcoming, the .cache should contain
both executables and debuginfo, and then zip-packing up the
cache should fulfill this use case with existing elfutils code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.