Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] Add debuginfod support to GDB
Date: Thu, 09 Jan 2020 13:48:00 -0000	[thread overview]
Message-ID: <83pnfsaggp.fsf@gnu.org> (raw)
In-Reply-To: <CAJDtP-RzP1byHayyOcXeFjucf65mAt4bi9T28nC9zfJ_-0Md3w@mail.gmail.com>	(message from Aaron Merey on Wed, 8 Jan 2020 22:48:11 -0500)

> From: Aaron Merey <amerey@redhat.com>
> Date: Wed, 8 Jan 2020 22:48:11 -0500
> 
> +* GDB now supports debuginfod, an HTTP server for distributing
> +  ELF/DWARF debugging information as well as source code. When built with
> +  debuginfod, GDB can automatically query debuginfod servers for the
> +  separate debug files and source code of the executable being debugged.
> +  To build GDB with debuginfod, pass --with-debuginfod to configure.
> +  This requires libdebuginfod, the debuginfod client library.
> +  debuginfod is distributed with elfutils, starting with version 0.178.
> +  You can get the latest version from https://sourceware.org/elfutils.

This part is OK, but please leave 2 spaces between sentences, per our
conventions.

Thanks.


  reply	other threads:[~2020-01-09 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  3:48 Aaron Merey
2020-01-09 13:48 ` Eli Zaretskii [this message]
     [not found] ` <87h814r6p4.fsf@tromey.com>
2020-01-09 22:41   ` Aaron Merey
2020-01-09 23:28     ` Christian Biesinger via gdb-patches
2020-01-10 16:32       ` Aaron Merey
     [not found]     ` <87tv53wfub.fsf@tromey.com>
2020-01-10 16:46       ` Aaron Merey
2020-01-10 18:43         ` Tom Tromey

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=83pnfsaggp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=amerey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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