[PATCH 4/4] eu-stacktrace: add unwind origin diagnostics to eu-stack

2024-10-16 Thread Aaron Merey
Hi Serhei, On Tue, Oct 15, 2024 at 11:29 AM Serhei Makarov wrote: > > Since we obtain diagnostics about unwind method, another logical place > to show them is in eu-stack. > > This requires an additional pseudo-unwind type DWFL_UNWOUND_INLINE to > clarify what happens with entries for inlined f

[PATCH 3/4] eu-stacktrace: add unwind origin diagnostics

2024-10-16 Thread Aaron Merey
Hi Serhei, On Tue, Oct 15, 2024 at 11:28 AM Serhei Makarov wrote: > > Track the method used to unwind each Dwfl_Frame using an enum field > unwound_source; provide access to the field. Then use that in > eu-stacktrace to display the unwind methods used for each process. > > This is an important

[PATCH 2/4] eu-stacktrace: configury for initial version (x86/sysprof only)

2024-10-16 Thread Aaron Merey
Hi Serhei, On Tue, Oct 15, 2024 at 11:28 AM Serhei Makarov wrote: > > Due to the x86-specific code in the initial version the configury has > significant restrictions. If --enable-stacktrace is not explicitly > provided, then eu-stacktrace will be disabled by default when > x86 architecture or sy

[PATCH 1/4] eu-stacktrace: add eu-stacktrace tool

2024-10-16 Thread Aaron Merey
Hi Serhei, On Tue, Oct 15, 2024 at 11:27 AM Serhei Makarov wrote > eu-stacktrace: add eu-stacktrace tool > > eu-stacktrace is a utility to process a stream of raw stack > samples (such as those obtained from the Linux kernel's > PERF_SAMPLE_STACK facility) into a stream of stack traces (such as

[PATCH v2 5/6] Remove usage of "unlocked" variant of stdio print functions

2024-10-16 Thread Michael Pratt
These "unlocked" Linux Standard Base variants of standard functions are not available on some systems that are still capable of building Linux and ELFs. The difference is negligible for simple printing to stdout. POSIX also states for the similar putc_unlocked(): These functions can safely be

☺ Buildbot (Sourceware): elfutils - build successful (main)

2024-10-16 Thread builder
A restored build has been detected on builder elfutils-debian-ppc64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/63/builds/399 Build state: build successful Revision: 1fabae9c499359932fd5db5f0014ed0ab5257b65 Worker: debian-ppc64 B

Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)

2024-10-16 Thread Aaron Merey
On Wed, Oct 16, 2024 at 2:07 PM 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/398 > > Build state: failed test (failure) > Revision: 088ac

☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)

2024-10-16 Thread builder
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/398 Build state: failed test (failure) Revision: 088ac7726a935aa048f231bbb793c0fc2134cb51 Worker: debian-ppc64

Re: [PATCH 9/9] doc/Makefile.am: Add man pages

2024-10-16 Thread Aaron Merey
On Tue, Oct 15, 2024 at 6:01 PM Mark Wielaard wrote: > > On Wed, Oct 02, 2024 at 10:26:10PM -0400, Aaron Merey wrote: > > Add the following man pages to notrans_dist_man3_MANS: > > > > elf32_xlatetom.3 elf64_xlatetom.3 elf32_xlatetof.3 elf64_xlatetof.3 > > elf32_newphdr.3 elf64_newphdr.3 elf32_new

Re: [PATCH] PR32218: debuginfod-client: support very long source file

2024-10-16 Thread Mark Wielaard
Hi Frank, On Tue, 2024-10-15 at 18:12 -0400, Frank Ch. Eigler wrote: > > Is this 4-byte hash enough to prevent accidental collisions? > > Yeah, it only needs to be uniqueish among source files of the same > binary, and with the same #-escaped tail string. Aha, it is "under" an unique build-id al