public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 00/11] Aarch64 linux GDB native multi-arch debugging (part 1)
Date: Wed, 01 Jul 2015 17:00:00 -0000	[thread overview]
Message-ID: <55941CA2.90709@redhat.com> (raw)
In-Reply-To: <1435759111-22856-1-git-send-email-yao.qi@linaro.org>

On 07/01/2015 02:58 PM, Yao Qi wrote:
> This patch series is to enable Aarch64 GDB (64-bit) debug arm program
> (32-bit) rudimentarily, which means with these patches applied, Aarch64
> GDB is able to do some basic debugging to arm program .  However, some
> features are still missing,
> 
>  - Debug multi-threaded program,
>  - Use HW watchpoint and breakpoint,
> 
> because current linux kernel ptrace doesn't have right requests to get
> the TLS area and to set HW watchpoint registers.  I am still working
> with kernel hackers to get ptrace requests ready.  Our plan is to be
> clear on aarch64 multi-arch debugging requirements to kernel first,
> get them upstream to kernel, and then, post the rest of aarch64 gdb
> multi-arch patches.  Afterwards, I'll add aarch64 multi-arch support
> in gdbserver too.

I'd be fantastic if you managed to merge the gdb and gdbserver
arm/aarch64 files, like we did for x86.

> 
> Patch #1 is to align arm-linux-nat.c to aarch64-linux-nat.c, it is a
> refactor patch.  Patch #2 and #3 starts the basic multi-arch debugging
> support, in which some code is shared between arm and aarch64.  Patch
> #4 is to adjust all arm-*.xml target descriptions to fix some fails
> I've seen.  Patch #5 - #8 are various tweaks to gdb testsuite for
> aarch64 multi-arch debugging.

I skimmed these and they looked fine to me.

> 
> Patch #9 - #11 can be regarded as an RFC, which teaches GDB to use
> hardware single step in software single step architecture if target
> supports hardware single step.  They are useful to aarch64 multi-arch
> debugging, because hardware single step is available for arm32 process
> on aarch64.

These I think are problematic as is.

> 
> The whole series is tested on aarch64-linux with both aarch64 gcc and
> arm gcc.  It is also tested on arm-linux and x86_64-linux.  Since we'll
> branch 7.10 soon, I don't like to have such big change at last moment
> of branching and releasing.  I plan to push them (or part of them) in
> after 7.10 branch is created, if there are no objections.
> 

Thanks,
Pedro Alves

  parent reply	other threads:[~2015-07-01 17:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 13:58 Yao Qi
2015-07-01 13:58 ` [PATCH 07/11] New proc is_aarch32_target Yao Qi
2015-07-01 13:58 ` [PATCH 08/11] New proc is_aarch64_target Yao Qi
2015-07-01 14:10   ` Andreas Schwab
2015-07-01 14:19     ` Yao Qi
2015-07-01 14:39       ` Andreas Schwab
2015-07-01 13:58 ` [PATCH 01/11] Remove {fetch,store}_fpregister and {fetch,store}_register Yao Qi
2015-07-01 13:58 ` [PATCH 02/11] New aarch32-linux-nat.c Yao Qi
2015-07-01 13:58 ` [PATCH 04/11] Set architecture to arm in arm-*.xml files Yao Qi
2015-07-01 13:59 ` [PATCH 03/11] Native debug arm program by aarch64 GDB Yao Qi
2015-07-01 13:59 ` [PATCH 09/11] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step Yao Qi
2015-07-01 13:59 ` [PATCH 06/11] Enable multi-arch test in catch-syscall.exp on aarch64 Yao Qi
2015-07-01 13:59 ` [PATCH 10/11] Reply s and S vCont actions if target supports hardware single step Yao Qi
2015-07-01 13:59 ` [PATCH 05/11] Adjust gdb.multi tests for aarch64 Yao Qi
2015-07-01 13:59 ` [PATCH 11/11] New target_ops hook to_can_do_single_step Yao Qi
2015-07-01 16:43   ` Pedro Alves
2015-07-02  8:56     ` Yao Qi
2015-07-02  9:09       ` Pedro Alves
2015-07-01 17:00 ` Pedro Alves [this message]
2015-07-01 18:54   ` [PATCH 00/11] Aarch64 linux GDB native multi-arch debugging (part 1) Pedro Alves
2015-07-02  9:05   ` Yao Qi
2015-07-07 16:13   ` Yao Qi

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=55941CA2.90709@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).