From: Pedro Alves <palves@redhat.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [pushed 8.0-branch] [Bug server/22137] gdbserver crashes on hosts with pkru register
Date: Mon, 16 Oct 2017 13:44:00 -0000 [thread overview]
Message-ID: <f3f445d9-1845-8f83-cb83-f0ab61bdccf9@redhat.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B197A9A2DC4@IRSMSX104.ger.corp.intel.com>
On 10/16/2017 02:20 PM, Tedeschi, Walfred wrote:
>
>>> > > I also couldn't compile master:
>>> > > ../../../binutils-gdb/gdb/probe.c: In function \u2018void
>> > parse_probes_in_pspace(const probe_ops*, program_space*, const char*,
>> > const char*, const char*, std::vector<symtab_and_line>*)\u2019:
>>> > > ../../../binutils-gdb/gdb/probe.c:68:12: error: types may not be defined in a
>> > for-range-declaration [-Werror]
>>> > > for (struct probe *probe : probes)
>>> > > ^~~~~~
>>> > > ../../../binutils-gdb/gdb/probe.c: In function \u2018VEC_probe_p*
>> > find_probes_in_objfile(objfile*, const char*, const char*)\u2019:
>>> > > ../../../binutils-gdb/gdb/probe.c:213:8: error: types may not be defined in a
>> > for-range-declaration [-Werror]
>>> > > for (struct probe *probe : probes)
>>> > > ^~~~~~
>>> > >
>>> > > Are you aware of it?
>> >
>> > Yes, it's a GCC bug:
>> > https://sourceware.org/ml/gdb-patches/2017-09/msg00270.html
>> >
>> > What is your gcc version?
>> >
>> > I don't see this myself, but I know that Keith also ran into this recently. If it's
>> > easy to work around it, I don't see why not.
>> >
>> > Does this work for you?
>> >
> It worked!
Thanks, I'll push in a bit. I'm still curious to
know your gcc version though.
Actually, I'm confused on how it worked for you, since
I hadn't fixed the same problem around line "213" quoted
above.
Are you sure you tested with the same compiler?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-10-16 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 8:30 Tedeschi, Walfred
2017-10-16 12:49 ` Pedro Alves
2017-10-16 13:20 ` Tedeschi, Walfred
2017-10-16 13:44 ` Pedro Alves [this message]
2017-10-16 14:04 ` Tedeschi, Walfred
2017-10-16 14:16 ` Pedro Alves
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=f3f445d9-1845-8f83-cb83-f0ab61bdccf9@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=walfred.tedeschi@intel.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