Hi,
On Mon, 2019-10-28 at 15:06 -0400, Frank Ch. Eigler wrote:
> From 3e1f8d93569004d06902459d84baceb636e139d5 Mon Sep 17 00:00:00 2001
> From: Aaron Merey
> Date: Mon, 28 Oct 2019 13:29:26 -0400
> Subject: [PATCH 1/2] debuginfod 1/2: client side
>
> Introduce the debuginfod/ subdirectory, conta
Hi -
> A few comments on the first (top-level) part, just to make progress.
Thanks.
> > diff --git a/config/libdebuginfod.pc.in b/config/libdebuginfod.pc.in
> No Requires on libelf or libdw?
Correct, the debuginfo client code does not call into elfutils.
> My only concern is that these might
Hi,
On Mon, 2019-10-28 at 15:06 -0400, Frank Ch. Eigler wrote:
> Introduce the debuginfod/ subdirectory, containing the client for a
> new debuginfo-over-http service, in shared-library and command-line
> forms. Two functions in libdwfl make calls into the client library to
> fetch elf/dwarf file
Hi Jonathon,
On Mon, 2019-11-11 at 17:38 -0600, Jonathon Anderson wrote:
> > Since the memblocks are per thread, it seems we could easily back out
> > an allocation we don't need as long as the thread hasn't done any
> > other
> > allocation from the memblock. What do you think of the attached pa
Hi Frank,
On Tue, 2019-11-12 at 10:14 -0500, Frank Ch. Eigler wrote:
> > My only concern is that these might slow down configure when
> > debuginfod
> > isn't enabled? Can/Should they be moved later after the enable
> > test?
>
> It'd be fractions of a second per configure run ... worth worrying
