Re: gdb ignoring vCont supported commands
Bill Morgan <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAM4wpo9uzGxSKdJfpUFKg4hSSxrNAebDyDnwf3vgs34+cpge_g@mail.gmail.com> |
On Tue, Oct 9, 2018 at 4:12 PM Pedro Alves <[email protected]> wrote: > On 10/09/2018 09:29 PM, Bill Morgan wrote: > > On Tue, Oct 9, 2018 at 3:16 PM Simon Marchi <[email protected]> > 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. > > Thanks, > Pedro Alves >