From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B823F3858D39; Tue, 27 Dec 2022 16:02:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B823F3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672156968; bh=DSXrH6I4xmqatFSpJYVpw7WOwBkFAoLMxj61H933St0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=T268z0IcRq20RduGKMR1zz63M5Kg1s6g17ieIwna6O0KHqBGwclRaz+6WCHDejBUn WpGRU6sUxHr/B5BbBfUDf6/3y+U9KRU+rM9kWHNAlVK2i28g2eybIpHrR7pn07jE5T pIDFcddYBWOmdEWx2a/GFgbqrK94a13lzU07W/28= From: "dodji at redhat dot com" To: libabigail@sourceware.org Subject: [Bug default/29932] abidiff coredump at abg-dwarf-reader.cc:lookup_fn_type_from_die_repr_per_tu when read libc.so from glibc Date: Tue, 27 Dec 2022 16:02:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: dodji at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29932 --- Comment #3 from dodji at redhat dot com --- (In reply to Xiaole He from comment #2) > (In reply to dodji from comment #1) > > This should be fixed by commit > > https://sourceware.org/git/?p=3Dlibabigail.git;a=3Dcommit; > > h=3Dde45f1e69b96a1f7511c94837e1793136b384407 in the master branch of th= e Git > > repository. > >=20 > > The fix should be available in the coming 2.3 version of libabigail. >=20 > Thank you agin, dodji, for using your precious time in resolving this > problem. I already verified that this problem has disappeared using the > updated master branch of git repository. How amazing man you are, good jo= b! You are too kind :-) Thank *YOU* for taking the time to report these problems. That's the first step that allows us to have a better system overall. So really thank you f= or reporting these issues. And sorry for the inconvenience. --=20 You are receiving this mail because: You are on the CC list for the bug.=