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: Thu, 18 Oct 2018 13:42:00 -0000 [thread overview]
Message-ID: <CAM4wpo9LC_n8dQmPGuBHK0PXkbnic96dF=MMgOf7L+TNWcAEAw@mail.gmail.com> (raw)
In-Reply-To: <a1a26ad1-b1ae-04c5-20ca-c891676f938c@redhat.com>
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:
> >
> > 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, 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?
diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
index 53eee76926..721675266c 100644
--- a/gdb/arm-tdep.c
+++ b/gdb/arm-tdep.c
@@ -6221,7 +6221,24 @@ arm_get_next_pcs_addr_bits_remove (struct
arm_get_next_pcs *self,
static CORE_ADDR
arm_get_next_pcs_syscall_next_pc (struct arm_get_next_pcs *self)
{
- return 0;
+ CORE_ADDR next_pc = 0;
+ CORE_ADDR pc = regcache_read_pc (self->regcache);
+ int is_thumb = arm_is_thumb (self->regcache);
+
+ /* Without the knowledge of the OS (if any) we need to assume that the
next
+ user-mode instruction is executed */
+
+ if (is_thumb)
+ {
+ next_pc = pc + 2;
+ }
+
+ else
+ {
+ next_pc = pc + 4;
+ }
+
+ return next_pc;
}
/* Wrapper over arm_is_thumb for use in arm_get_next_pcs. */
@@ -9384,6 +9401,7 @@ arm_gdbarch_init (struct gdbarch_info info, struct
gdbarch_list *arches)
set_gdbarch_sw_breakpoint_from_kind (gdbarch,
arm_sw_breakpoint_from_kind);
set_gdbarch_breakpoint_kind_from_current_state (gdbarch,
arm_breakpoint_kind_from_current_state);
+ set_gdbarch_software_single_step( gdbarch, arm_software_single_step );
/* Information about registers, etc. */
set_gdbarch_sp_regnum (gdbarch, ARM_SP_REGNUM);
next prev parent reply other threads:[~2018-10-18 13:42 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
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 [this message]
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='CAM4wpo9LC_n8dQmPGuBHK0PXkbnic96dF=MMgOf7L+TNWcAEAw@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