Re: gdb ignoring vCont supported commands
Pedro Alves <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
On 10/18/2018 02:42 PM, Bill Morgan wrote: > On Tue, Oct 9, 2018 at 4:12 PM Pedro Alves <[email protected]> wrote: > >> On 10/09/2018 09:29 PM, Bill Morgan wrote: >>> >>> 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. >> > > I couldn't get the change on the other thread to work, What change do you mean? > but this has been > reported before and a patch submitted to fix it. > > https://sourceware.org/bugzilla/show_bug.cgi?id=21272 > > I only needed this portion of the patch to get it working. > > Any chance on getting it merged to master? > No, sorry -- that would make gdb always use software single-step, even if the stub/probe supports hw stepping. Not sure about the arm_get_next_pcs_syscall_next_pc change, but I suppose that it helps with most syscalls. See <https://sourceware.org/gdb/wiki/ContributionChecklist>. Thanks, Pedro Alves