From: Ben Woodard <woodard@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: libabigail 2.1 trunk testing where are we?
Date: Fri, 29 Jul 2022 15:48:39 -0700 [thread overview]
Message-ID: <AA281ED8-7C27-4EEE-9282-AE38E4CF9D6A@redhat.com> (raw)
In-Reply-To: <YuRJpWXXz+I/BI08@wildebeest.org>
Thanks for the patch.
I put it into my personal develop tree and it relatively immediately fixed 4/6 of the packages that I had identified as having that problem. The tests on the other two packages are still running and have been running for over half an hour and so something is working. We will see if they complete before they timeout. I may have to move those two to the takes to long to compete group https://sourceware.org/bugzilla/show_bug.cgi?id=29303
So this at least fixed:
guile22
guile30
gnucash
aisleriot
I don’t yet have data on:
gdb-headless
sagemath
-ben
> On Jul 29, 2022, at 1:57 PM, Mark Wielaard <mark@klomp.org> wrote:
>
> On Fri, Jul 29, 2022 at 11:28:18AM -0700, Ben Woodard via Libabigail wrote:
>> 1 crash due to incorrect ELF in that shows up in a small number of
>> packages https://sourceware.org/bugzilla/show_bug.cgi?id=29346
>
> I have a patch that should work around that on:
> https://code.wildebeest.org/git/user/mjw/libabigail/commit/?h=pr29346
> Also attached. Maybe someone with commit access could push it to a
> users try branch for testing?
>
> Thanks,
>
> Mark<0001-Handle-zero-sh_entsize-in-get_soname_of_elf_file.patch>
next prev parent reply other threads:[~2022-07-29 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 18:28 Ben Woodard
2022-07-29 20:57 ` Mark Wielaard
2022-07-29 22:48 ` Ben Woodard [this message]
2022-09-20 8:47 ` Dodji Seketeli
2022-09-20 15:05 ` Mark Wielaard
2022-09-25 7:06 ` Dodji Seketeli
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=AA281ED8-7C27-4EEE-9282-AE38E4CF9D6A@redhat.com \
--to=woodard@redhat.com \
--cc=libabigail@sourceware.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).