On Fri, 2020-02-21 at 13:49 +0100, Mark Wielaard wrote:
> If DEBUGINFOD_URLS is set various tests will try to query the debuginfod
> server which can stall the tests a bit. If other evironment variables
> like DEBUGINFOD_PROGRESS are set it will make various tests fail because
> the expected output
Hi -
This patch has been baking on my public servers awhile and can make a
huge difference in performance. It's not something immediately
obvious how or whether to test, as it's a pure performance improvement.
Planning to push shortly.
commit ae8b89716116a6df124f8700f77460b5e97c12c4 (origin/fche
https://sourceware.org/bugzilla/show_bug.cgi?id=25369
Frank Ch. Eigler changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |fche at redhat dot com
---
Hi -
As a part of PR25369, I propose this small set of client api
extensions, requested by gdb developers and needed by personal
experience. (I plan to roll it out on my debuginfod servers shortly
to let it soak.) An end-user visible immediate difference is in the
DEBUGINFOD_PROGRESS=1 format me
On 2020-02-24 10:35 p.m., Frank Ch. Eigler wrote:
> Hi -
>
> As a part of PR25369, I propose this small set of client api
> extensions, requested by gdb developers and needed by personal
> experience. (I plan to roll it out on my debuginfod servers shortly
> to let it soak.) An end-user visible