From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit aa17805fb9a3a1983a510ba425b682fba03410c2 might be unfortunate
Date: Fri, 13 Sep 2019 01:32:00 -0000 [thread overview]
Message-ID: <20190913013155.GS6076@embecosm.com> (raw)
In-Reply-To: <aa17805fb9a3a1983a510ba425b682fba03410c2-master-breakage@gdb-build>
* gdb-buildbot@sergiodj.net <gdb-buildbot@sergiodj.net> [2019-09-12 21:04:31 -0400]:
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> gdb: Have 'maint info sections' print all sections again
> aa17805fb9a3a1983a510ba425b682fba03410c2
>
> might have made GDB unwell. Since I am just your Butler BuildBot,
> I kindly ask that a human superior officer double-check this.
>
> Please note that if you are reading this message on gdb-patches, there might
> be other builders broken.
Apologies for causing this breakage.
I have pushed the patch below which should resolve this issue.
Thanks,
Andrew
--
commit ec6c8338a89b0ec022b66ed3efdd1577e6449d6d
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Thu Sep 12 21:23:37 2019 -0400
gdb: Force use of float version of log10
This commit:
commit aa17805fb9a3a1983a510ba425b682fba03410c2
Date: Sat Aug 31 23:44:40 2019 +0100
gdb: Have 'maint info sections' print all sections again
introduced a use of log10 that took an int as a parameter.
Unfortunately this was causing a compilation error on Solaris, see:
https://sourceware.org/ml/gdb-patches/2019-09/msg00230.html
https://sourceware.org/ml/gdb-patches/2019-09/msg00231.html
because there was only a float, double, or long double version of
log10, and the compiler doesn't know which to choose.
This commit should resolve this issue by casting the argument to
float.
gdb/ChangeLog:
* maint.c (maint_print_section_data::maint_print_section_data):
Force use of 'float log10 (float)' by casting the argument to
float.
diff --git a/gdb/maint.c b/gdb/maint.c
index 286ec310135..1a621a17191 100644
--- a/gdb/maint.c
+++ b/gdb/maint.c
@@ -301,7 +301,7 @@ struct maint_print_section_data
arg(arg)
{
int section_count = gdb_bfd_count_sections (abfd);
- index_digits = ((int) log10 (section_count)) + 1;
+ index_digits = ((int) log10 ((float) section_count)) + 1;
}
private:
prev parent reply other threads:[~2019-09-13 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 1:04 gdb-buildbot
2019-09-13 1:04 ` Breakage on builder Solaris11-sparcv9-m64, revision aa17805fb9a3a1983a510ba425b682fba03410c2 gdb-buildbot
2019-09-13 1:11 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-09-13 1:32 ` Andrew Burgess [this message]
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=20190913013155.GS6076@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@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