From: Dodji Seketeli <dodji@seketeli.org>
To: Mark Wielaard <mark@klomp.org>
Cc: libabigail@sourceware.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Wed, 28 Oct 2020 10:30:12 +0100 [thread overview]
Message-ID: <874kmeaeaj.fsf@seketeli.org> (raw)
In-Reply-To: <55435f4245c90de7b3e68997aaa085d12765ea7b.camel@klomp.org> (Mark Wielaard's message of "Tue, 27 Oct 2020 14:12:37 +0100")
Hello Mark,
Mark Wielaard <mark@klomp.org> a écrit:
Thank you for looking into this!
[...]
> From d7253e475b6d04445d62ae5b55c03facbd6ab87d Mon Sep 17 00:00:00 2001
> From: Mark Wielaard <mark@klomp.org>
> Date: Tue, 27 Oct 2020 14:06:03 +0100
> Subject: [PATCH] Assume subrange bounds types are unsigned if no underlying
> type is given.
>
> When running abidiff on test34-libjemalloc.so.2-intel-16.0.3 it would
> crash in array_type_def::subrange_type::get_length on the ABG_ASSERT
> get_upper_bound() >= get_lower_bound(). This was because that file
> contained a subrange upper_bound value encoded with data1 or data2
> without an underlying type. In that case we assumed the value was
> encoded as a signed value which caused some of the upper bounds to
> be negative (while the lower bound, which wasn't given, was assumed
> to be zero).
>
> * src/abg-dwarf-reader.cc (build_subrange_type): Default
> is_signed to false.
>
> Signed-off-by: Mark Wielaard <mark@klomp.org>
Applied to master.
Thanks!
--
Dodji
next prev parent reply other threads:[~2020-10-28 9:30 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 9:47 buildbot
2020-10-27 11:30 ` Mark Wielaard
2020-10-27 13:12 ` Mark Wielaard
2020-10-28 9:30 ` Dodji Seketeli [this message]
2020-10-28 10:12 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 13:19 buildbot
2021-12-21 19:18 buildbot
2021-12-14 15:55 buildbot
2021-12-15 13:01 ` Mark Wielaard
2021-11-29 8:05 buildbot
2021-11-29 11:23 ` Mark Wielaard
2021-10-27 11:11 buildbot
2021-10-27 11:14 ` Mark Wielaard
2021-10-27 12:04 ` Dodji Seketeli
2021-10-18 10:58 buildbot
2021-09-23 12:12 buildbot
2021-09-23 12:19 ` Mark Wielaard
2021-08-11 17:08 buildbot
2021-07-16 10:11 buildbot
2021-07-16 10:33 ` Mark Wielaard
2021-04-12 15:48 buildbot
2021-03-18 16:05 buildbot
2021-03-19 23:03 ` Mark Wielaard
2020-12-02 15:32 buildbot
2020-11-27 16:59 buildbot
2020-11-25 12:52 buildbot
2020-11-25 8:51 buildbot
2020-11-12 10:50 buildbot
2020-11-02 17:21 buildbot
2020-10-14 10:31 buildbot
2020-10-09 9:35 buildbot
2020-07-30 15:29 buildbot
2020-07-30 15:38 ` Mark Wielaard
2020-07-28 14:40 buildbot
2020-07-28 14:41 ` Mark Wielaard
2020-05-04 9:36 buildbot
2020-04-23 13:09 buildbot
2020-04-23 13:32 ` Mark Wielaard
2020-03-26 15:47 buildbot
2020-03-19 10:55 buildbot
2020-03-19 12:25 ` Mark Wielaard
2020-03-20 22:23 ` Dodji Seketeli
2020-03-12 13:41 buildbot
2020-01-01 0:00 buildbot
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Matthias Maennich via libabigail
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Matthias Maennich via libabigail
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2018-01-01 0:00 buildbot
2018-01-01 0:00 ` Mark Wielaard
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=874kmeaeaj.fsf@seketeli.org \
--to=dodji@seketeli.org \
--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).