Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Aaron Merey <amerey@redhat.com>,
	gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH 3/3] PR gdb/27570: missing support for debuginfod in core_target::build_file_mappings
Date: Wed, 3 Nov 2021 21:37:30 -0400	[thread overview]
Message-ID: <c56ce06f-b855-f084-7c3d-6ae0cef6e3d0@polymtl.ca> (raw)
In-Reply-To: <20210812042406.75637-4-amerey@redhat.com>

On 2021-08-12 00:24, Aaron Merey wrote:
> Add debuginfod support to core_target::build_file_mappings and
> locate_exec_from_corefile_build_id to enable the downloading of
> missing core file executables and shared libraries.
> 
> Also add debuginfod support to solib_map_sections so that previously
> downloaded shared libraries can be retrieved from the debuginfod
> cache.
> 
> When core file shared libraries are found locally, verify
> that their build-ids match the corresponding build-id found in
> the core file.  If there is a mismatch, print a warning and attempt
> to query debuginfod for the correct build of the shared library:
> 
> warning: Build-id of /lib64/libc.so.6 does not match core file.
> Downloading XY.Z MB executable for /lib64/libc.so.6

Since this is getting a bit old, it doesn't apply anymore.  Can you send
a new version of the series (including fixes to patch 2)?

Thanks

Simon

  parent reply	other threads:[~2021-11-04  1:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  4:24 [PATCH v3 0/3] Add debuginfod core file support Aaron Merey via Gdb-patches
2021-08-12  4:24 ` [PATCH 1/3] gdb/solib: Refactor scan_dyntag Aaron Merey via Gdb-patches
2021-08-17 13:28   ` Simon Marchi via Gdb-patches
2021-08-19  2:30     ` Aaron Merey via Gdb-patches
2021-08-12  4:24 ` [PATCH 2/3] gdb: Add soname to build-id mapping for corefiles Aaron Merey via Gdb-patches
2021-08-15 14:51   ` Lancelot SIX via Gdb-patches
2021-08-17 13:58     ` Simon Marchi via Gdb-patches
2021-08-19  2:22       ` Aaron Merey via Gdb-patches
2021-09-29  1:12         ` Aaron Merey via Gdb-patches
2021-10-18 23:06           ` [PING**2][PATCH " Aaron Merey via Gdb-patches
2021-11-03 18:12             ` [PING**3][PATCH " Aaron Merey via Gdb-patches
2021-11-04  1:32         ` [PATCH " Simon Marchi via Gdb-patches
2021-08-12  4:24 ` [PATCH 3/3] PR gdb/27570: missing support for debuginfod in core_target::build_file_mappings Aaron Merey via Gdb-patches
2021-09-29  1:13   ` Aaron Merey via Gdb-patches
2021-10-18 23:05     ` [PING**2][PATCH " Aaron Merey via Gdb-patches
2021-11-03 18:11       ` [PING**3][PATCH " Aaron Merey via Gdb-patches
2021-11-04  1:37   ` Simon Marchi via Gdb-patches [this message]
2021-11-10  1:47 [PATCH v4 0/3] Add debuginfod core file support Aaron Merey via Gdb-patches
2021-11-10  1:47 ` [PATCH 3/3] PR gdb/27570: missing support for debuginfod in core_target::build_file_mappings Aaron Merey via Gdb-patches
2021-11-14  2:56   ` Simon Marchi via Gdb-patches
2021-11-17  3:28     ` Aaron Merey via Gdb-patches
2022-01-26  1:42       ` Aaron Merey via Gdb-patches
2022-02-09  2:31         ` Aaron Merey via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c56ce06f-b855-f084-7c3d-6ae0cef6e3d0@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=amerey@redhat.com \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox