From: "hexiaole1994 at 126 dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29934] abidiff coredump at abg-comparison.cc:ensure_lookup_tables_populated when read libdovecot-storage.so and libdovecot-sieve.so from dovecot
Date: Mon, 26 Dec 2022 03:40:51 +0000 [thread overview]
Message-ID: <bug-29934-9487-UDhvnCzIFf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29934-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29934
--- Comment #3 from Xiaole He <hexiaole1994 at 126 dot com> ---
(In reply to dodji from comment #2)
> Hello,
>
> This issue should hopefully be fixed in the master branch of the git
> repository at
> https://sourceware.org/git/?p=libabigail.git;a=commit;
> h=e3725f1b96ad2e935290bea8be7925f2a8cc3c89.
>
> The fix should be available in the coming 2.3 version of libabigail.
>
> Thank you for reporting this issue and sorry for the inconvenience.
Thank you, dodji, for using your precious time in resolving this problem.
I using the updated master branch of git,
e3725f1b96ad2e935290bea8be7925f2a8cc3c89 (Bug 29934 - Handle buggy data members
with empty names), to verify that the problem of 'libdovecot-storage.so' has
been disappeared, but the similar problem of 'libdovecot-sieve.so' that caused
coredump still exist, sorry for disturbing you again and the reproducing steps
of 'libdovecot-storage.so' was wroten at the first comment of this page.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-26 3:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 11:49 [Bug default/29934] New: " hexiaole1994 at 126 dot com
2022-12-22 11:55 ` [Bug default/29934] " hexiaole1994 at 126 dot com
2022-12-24 13:26 ` dodji at redhat dot com
2022-12-24 14:12 ` dodji at redhat dot com
2022-12-26 3:40 ` hexiaole1994 at 126 dot com [this message]
2022-12-26 14:13 ` dodji at redhat dot com
2022-12-29 10:35 ` dodji at redhat dot com
2022-12-29 14:54 ` hexiaole1994 at 126 dot com
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=bug-29934-9487-UDhvnCzIFf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).