From: Bill Morgan <arthurwilliammorgan@gmail.com>
To: palves@redhat.com
Cc: Simon Marchi <simon.marchi@polymtl.ca>, gdb@sourceware.org
Subject: Re: gdb ignoring vCont supported commands
Date: Tue, 09 Oct 2018 21:34:00 -0000 [thread overview]
Message-ID: <CAM4wpo_k75781wwrkYVxJ+jE0k0tuD4V=OMzwij_V2tvcD=_eg@mail.gmail.com> (raw)
In-Reply-To: <CAM4wpo9uzGxSKdJfpUFKg4hSSxrNAebDyDnwf3vgs34+cpge_g@mail.gmail.com>
On Tue, Oct 9, 2018 at 4:16 PM Bill Morgan <arthurwilliammorgan@gmail.com>
wrote:
>
>
> On Tue, Oct 9, 2018 at 4:12 PM Pedro Alves <palves@redhat.com> wrote:
>
>> 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?
>>
>
> Custom OS on ARM.
>
> This is what I'm reporting to GDB:
>
> Sending packet: $qXfer:features:read:target.xml:0,fff#7d...Ack
> Packet received: l<target><architecture>arm</architecture></target>
>
>
>
>>
>> We're missing the small infrastructure change in GDB
>> mentioned in the discussion I linked before.
>>
>
What does GDB need to know about my OS for using software breakpoints for
stepping? From looking at this document:
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0036b/IHI0036B_bsabi.pdf
I'd be using the ARM Architecture Procedure Call Standard and probably be
considered Bare Metal. Although I have some ELF processes loaded and
running, I think that should be opaque to GDB though. My stub switches MMU
TTB as necessary for writing the software breakpoints to memory.
Could I report an existing OS to GDB?
>> Thanks,
>> Pedro Alves
>>
>
next prev parent reply other threads:[~2018-10-09 21:34 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
2018-10-09 21:17 ` Bill Morgan
2018-10-09 21:34 ` Bill Morgan [this message]
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='CAM4wpo_k75781wwrkYVxJ+jE0k0tuD4V=OMzwij_V2tvcD=_eg@mail.gmail.com' \
--to=arthurwilliammorgan@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--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