From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Enable range stepping for ARM on GDBServer
Date: Thu, 01 Sep 2016 17:02:00 -0000 [thread overview]
Message-ID: <f8a51842-a06c-8e21-e8a0-f765065a9537@redhat.com> (raw)
In-Reply-To: <CAH=s-PN-T_VVrjF2tf71wD15mLALEHbd3Wy_DA2duDrFYnqXmQ@mail.gmail.com>
On 09/01/2016 05:44 PM, Yao Qi wrote:
> Beside "removing reinsert_breakpoint on gdbserver internal event", we'd
> better to think that "each backend unwinders don't have to worry about
> unavailable data". I posted a draft here
> https://sourceware.org/ml/gdb-patches/2016-05/msg00060.html, I need
> some review comments. Pedro,
> can you take a look? This is not a hard requirement for ARM tracepoint
> support.
I plan to, but there a few things still blocking 7.12 that I'd like to
clear first.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-09-01 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 17:14 [PATCH 1/2] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 Antoine Tremblay
2016-08-31 17:14 ` [PATCH 2/2] Enable range stepping for ARM on GDBServer Antoine Tremblay
2016-08-31 17:50 ` Pedro Alves
2016-08-31 18:15 ` Antoine Tremblay
2016-08-31 18:39 ` Pedro Alves
2016-08-31 19:14 ` Antoine Tremblay
2016-09-01 13:37 ` Pedro Alves
2016-09-01 15:21 ` Antoine Tremblay
2016-09-01 15:59 ` Pedro Alves
2016-09-01 16:44 ` Yao Qi
2016-09-01 17:02 ` Pedro Alves [this message]
2016-09-01 17:06 ` Antoine Tremblay
2016-09-01 16:46 ` Antoine Tremblay
2016-09-18 19:58 ` Yao Qi
2016-08-31 17:40 ` [PATCH 1/2] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 Pedro Alves
2016-08-31 17:50 ` Antoine Tremblay
2016-08-31 17:52 ` Pedro Alves
2016-08-31 18:25 ` Antoine Tremblay
2016-08-31 19:16 ` Antoine Tremblay
2016-09-01 13:09 ` Pedro Alves
2016-09-01 15:12 ` Antoine Tremblay
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=f8a51842-a06c-8e21-e8a0-f765065a9537@redhat.com \
--to=palves@redhat.com \
--cc=antoine.tremblay@ericsson.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).