From: "hexiaole1994 at 126 dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29829] abidiff coredump at abg-dwarf-reader.cc when read libxul.so
Date: Tue, 29 Nov 2022 01:01:37 +0000 [thread overview]
Message-ID: <bug-29829-9487-0BOlsCC9gX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29829-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29829
--- Comment #2 from Xiaole He <hexiaole1994 at 126 dot com> ---
(In reply to dodji from comment #1)
> Hello,
>
> Thank you for reporting this problem.
>
> What version of libabigail/abidiff are you using?
>
> Is it possible to try to reproduce the issue with the last version of
> libabigail from the master branch of the git repository at
> https://sourceware.org/git/?p=libabigail.git;a=summary?
Thank you for replying, this problem was reproduced with libabigail of version
1.6, 2.0, 2.1. And we try to use the latest master branch of the git repository
to see whether it can be fixed, but it was reproduced again:
- git repo: git://sourceware.org/git/libabigail.git
- branch: master
- HEAD commit that reproduce against:
7bd69830520f2e7ce4efb989b5fd23fde316c7c1(Make Front Ends first class citizens)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-29 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 3:43 [Bug default/29829] New: " hexiaole1994 at 126 dot com
2022-11-28 16:29 ` [Bug default/29829] " dodji at redhat dot com
2022-11-29 1:01 ` hexiaole1994 at 126 dot com [this message]
2022-12-01 10:31 ` dodji at redhat dot com
2022-12-02 3:44 ` hexiaole1994 at 126 dot com
2022-12-02 16:19 ` dodji at redhat dot com
2022-12-02 23:46 ` 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-29829-9487-0BOlsCC9gX@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).