From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit de52b9607d2623f18b7a7dbee3e1123d8d63f5da might be unfortunate
Date: Sat, 30 Jun 2018 01:39:00 -0000 [thread overview]
Message-ID: <87k1qh59ys.fsf@redhat.com> (raw)
In-Reply-To: <20180629233540.GJ2511@adacore.com> (Joel Brobecker's message of "Fri, 29 Jun 2018 16:35:40 -0700")
On Friday, June 29 2018, Joel Brobecker wrote:
>> I'm still seeing a breakage here on x86-64 Fedora GNU/Linux, when
>> building gdbserver:
>>
>> ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c: In function ‘const target_desc* amd64_linux_read_description(uint64_t, bool)’:
>> ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c:121:67: error: too few arguments to function ‘target_desc* amd64_create_target_description(uint64_t, bool, bool, bool)’
>> *tdesc = amd64_create_target_description (xcr0, is_x32, true);
>> ^
>> In file included from ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c:26:0:
>> ../../../binutils-gdb/gdb/gdbserver/../arch/amd64.h:21:14: note: declared here
>> target_desc *amd64_create_target_description (uint64_t xcr0, bool is_x32,
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Does the patch below make sense? It fixes the breakage for me.
>
> Thanks for looking into it and the patch!
>
> I think the parameter should be set to "true". Otherwise, it will
> not include the fs_base and gs_base register in the list of registers.
> Although the name of the source file says x86, the code itself is
> protected by...
>
> #ifdef __x86_64__
>
> ... and is inside a function called amd64_linux_read_description.
> I also verified that this file gets compiled on amd64-linux platforms.
> See gdb/gdbserver/configure.srv:
>
> x86_64-*-linux*) srv_regobj="$srv_amd64_linux_regobj $srv_i386_linux_regobj"
>
> The last piece of confirmation is that setting the parameter to "true"
> provides the behavior before the parameter was added; and the reason
> for adding the parameter was to remove the {fs,gs}_base registers
> from the list for Windows only.
>
> Otherwise the rest (basically the ChangeLog) looks good.
Ah, thanks for the explanation. I should have investigated more before
sending the patch; I was doing something else and just wanted to make
GDB compile again. Glad I sent it here for your review!
> Thanks again!
No, I thank you!
I pushed the patch with s/false/true/, and your name in the ChangeLog.
>> diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
>> index 2fd2d90a49..743d465d81 100644
>> --- a/gdb/gdbserver/ChangeLog
>> +++ b/gdb/gdbserver/ChangeLog
>> @@ -1,3 +1,8 @@
>> +2018-06-29 Sergio Durigan Junior <sergiodj@redhat.com>
>> +
>> + * linux-x86-tdesc.c (amd64_linux_read_description): Add missing
>> + parameter in call to 'amd64_create_target_description'.
>> +
>> 2018-06-28 Jan Kratochvil <jan.kratochvil@redhat.com>
>>
>> * x86-tdesc.h: Remove executable permission flag.
>> diff --git a/gdb/gdbserver/linux-x86-tdesc.c b/gdb/gdbserver/linux-x86-tdesc.c
>> index 358659b295..7a45953dc9 100644
>> --- a/gdb/gdbserver/linux-x86-tdesc.c
>> +++ b/gdb/gdbserver/linux-x86-tdesc.c
>> @@ -118,7 +118,7 @@ amd64_linux_read_description (uint64_t xcr0, bool is_x32)
>>
>> if (*tdesc == NULL)
>> {
>> - *tdesc = amd64_create_target_description (xcr0, is_x32, true);
>> + *tdesc = amd64_create_target_description (xcr0, is_x32, true, false);
>>
>> init_target_desc (*tdesc, amd64_expedite_regs);
>> }
>
> --
> Joel
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-06-30 1:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 22:10 gdb-buildbot
2018-06-29 22:10 ` Breakage on builder RHEL-s390x-m64, revision de52b9607d2623f18b7a7dbee3e1123d8d63f5da gdb-buildbot
2018-06-29 22:10 ` Breakage on builder Fedora-s390x-m64, " gdb-buildbot
2018-06-29 22:12 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2018-06-29 22:21 ` Oh dear. I regret to inform you that commit de52b9607d2623f18b7a7dbee3e1123d8d63f5da might be unfortunate Joel Brobecker
2018-06-29 22:53 ` Joel Brobecker
2018-06-29 23:22 ` Sergio Durigan Junior
2018-06-29 23:35 ` Joel Brobecker
2018-06-30 1:39 ` Sergio Durigan Junior [this message]
2018-06-29 22:58 ` Breakage on builder Fedora-x86_64-m32, revision de52b9607d2623f18b7a7dbee3e1123d8d63f5da gdb-buildbot
2018-06-29 23:02 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-06-29 23:05 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-06-29 23:08 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2018-06-29 23:09 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-06-29 23:11 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-06-29 23:22 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-06-29 23:42 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-06-29 23:44 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2018-06-29 23:46 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
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=87k1qh59ys.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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