On Sat, Apr 23, 2022 at 01:19:53AM +, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-debian-ppc64 while
> building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/63/builds/4
>
> Build state: fai
A restored build has been detected on builder elfutils-fedora-x86_64 while
building elfutils.
Full details are available at:
http://localhost:8010/#builders/30/builds/19
Build state: build successful
Revision: aaa875db4d6dfa410903a08235a3c6cdc13842e5
Worker: fedora-x86_64
Build Reason: (unkn
A new failure has been detected on builder elfutils-debian-ppc64 while building
elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/63/builds/4
Build state: failed test (failure)
Revision: 7b046b7c060acc32c00748ee66ac350f77bc6571
Worker: debian-ppc64
Bu
Hi наб,
On Fri, Apr 15, 2022 at 02:12:31PM +0200, наб via Elfutils-devel wrote:
> On Fri, Apr 15, 2022 at 01:48:23PM +0200, Mark Wielaard wrote:
> > I have added a ChangeLog entry:
> >
> > 2022-01-19 Ahelenia Ziemiańska
> >
> >* profile.csh.in: Set DEBUGINFOD_URLS directly. Use "$0" an
Hi -
> - add_mhd_response_header (r, "X-DEBUGINFOD-SIZE",
> - to_string(fs.st_size).c_str());
> + rc = fstat (fd, &fs);
> + if (rc == 0)
> +add_mhd_response_header (r, "X-DEBUGINFOD-SIZE",
> +
I've updated the patch below with the changes Mark recommended.
A couple X-DEBUGINFOD-SIZE tests were added in another patch I recently
posted [1] that also fixes a bug when computing this header's value for
an archived file.
Aaron
[1] https://sourceware.org/pipermail/elfutils-devel/2022q2/0049
Please ignore the "2/2" in the subject line, this patch is not part of a series.
Aaron
For archived files X-DEBUGINFOD-SIZE currently contains the size of the
archive instead of the size of the uncompressed file. Fix this.
Also add testcases to verify X-DEBUGINFOD-SIZE contains uncompressed
file sizes.
Signed-off-by: Aaron Merey
---
debuginfod/debuginfod.cxx| 11
Hi,
On Thu, Mar 31, 2022 at 03:19:51PM +0200, Mark Wielaard via curl-library wrote:
> On Thu, Mar 31, 2022 at 04:00:16PM +0300, Catalin Raceanu via curl-library
> wrote:
> > On 31-Mar-22 15:04, Mark Wielaard wrote:
> > > whether there is a thread-safe way to call
> > > curl_global_init at a later
We used to go out of our way to initialize libcurl early before any other
thread/code was running. But this meant that we might pay startup cost,
which under FIPS is significant, even for code that never uses libdebuginfod
or TLS libcurl connections. Although curl_global_init itself isn't thread-sa
> Date: Sat, 16 Apr 2022 14:37:23 -0400
> Mark Wielaard writes:
>
> > I think we should drop this patch for now. Or are you still working on
> > it?
>
> Sure, let's drop it.
> Will bring in the xfail "cmd..." based one instead before too long.
>
> - FChE
- FChE
https://sourceware.org/bugzilla/show_bug.cgi?id=29082
--- Comment #3 from H.J. Lu ---
NT_GNU_PROPERTY_TYPE_0 is documented in
https://gitlab.com/x86-psABIs/Linux-ABI/-/wikis/uploads/0690db0a3b7e5d8a44e0271a4be54aa7/linux-gABI-and-or-2021-01-13.pdf
https://gitlab.com/x86-psABIs/x86-64-ABI/-/wikis
On Freitag, 15. April 2022 14:09:02 CEST Milian Wolff wrote:
> Hey there,
>
> a user reported broken symbol resolution in hotspot/perfparser which uses
> elfutils when he's using it on code compiled with LTO.
>
> I think I can reproduce this, and now spent some time trying to figure out
> the bre
https://sourceware.org/bugzilla/show_bug.cgi?id=29082
Martin Liska changed:
What|Removed |Added
CC||fweimer at redhat dot com,
14 matches
Mail list logo