From: Pedro Alves <palves@redhat.com>
To: Bill Morgan <arthurwilliammorgan@gmail.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: gdb ignoring vCont supported commands
Date: Tue, 09 Oct 2018 21:12:00 -0000 [thread overview]
Message-ID: <a1a26ad1-b1ae-04c5-20ca-c891676f938c@redhat.com> (raw)
In-Reply-To: <CAM4wpo9k2OCtHdwoO5EAaDk2uMqTrK48Nb+A33FP8Wds0vryqQ@mail.gmail.com>
On 10/09/2018 09:29 PM, Bill Morgan wrote:
> On Tue, Oct 9, 2018 at 3:16 PM Simon Marchi <simon.marchi@polymtl.ca> wrote:
>
>> On 2018-10-09 16:12, Bill Morgan wrote:
>>> I get a warning that vContSupported is unrecognized:
>>>
>>> Sending packet:
>>>
>> $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+#df...Ack
>>> Packet received:
>>>
>> PacketSize=3fff;QPassSignals+;qXfer:features:read+;qXfer:threads:read+;vContSupported
>>> Packet qSupported (supported-packets) is supported
>>> warning: unrecognized item "vContSupported" in "qSupported" response
>>
>> I believe you are missing the + after vContSupported.
>>
>> You are correct, I was missing the +. Thank you.
>
> So it is now recognizing the vContSupported, but it is still sending
> vCont;s
>
Argh, I forgot that this only really works on ARM GNU/Linux.
What is your target?
We're missing the small infrastructure change in GDB
mentioned in the discussion I linked before.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-10-09 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:42 Bill Morgan
2018-10-09 18:30 ` Pedro Alves
2018-10-09 20:12 ` Bill Morgan
2018-10-09 20:17 ` Simon Marchi
2018-10-09 20:29 ` Bill Morgan
2018-10-09 21:12 ` Pedro Alves [this message]
2018-10-09 21:17 ` Bill Morgan
2018-10-09 21:34 ` Bill Morgan
2018-10-19 13:40 ` Pedro Alves
2018-10-19 21:18 ` Bill Morgan
2018-10-11 17:23 ` Bill Morgan
2018-10-18 13:42 ` Bill Morgan
2018-10-19 13:35 ` Pedro Alves
2018-10-19 17:12 ` Bill Morgan
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=a1a26ad1-b1ae-04c5-20ca-c891676f938c@redhat.com \
--to=palves@redhat.com \
--cc=arthurwilliammorgan@gmail.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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