From: Yao Qi <qiyaoltc@gmail.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] Support tracepoints for ARM linux in GDBServer
Date: Wed, 27 Apr 2016 13:57:00 -0000 [thread overview]
Message-ID: <86a8kff93g.fsf@gmail.com> (raw)
In-Reply-To: <wwokbn4v1ci0.fsf@ericsson.com> (Antoine Tremblay's message of "Wed, 27 Apr 2016 08:07:19 -0400")
Antoine Tremblay <antoine.tremblay@ericsson.com> writes:
> Is your tree public somewhere btw ? As we're (Simon and I) almost done
> with the fast tracepoints if we can help with this (2. 3.) we would be
> glad to.
This tree https://github.com/qiyao/gdb/tree/arm-sw-single-step-2
includes two commits that
1) forces GDB use vCont;s with arm-linux gdbserver,
2) enable range stepping on arm-linux,
they'll cause some test failures, and you can start from them. I am not
sure what is the best fix could be so far, so I don't publish my fixes.
My patches might be completely wrong.
I don't mind if you guys jump in the muddy puddles together with me.
>
>>
>>> On my end we have fast tracepoints for arm almost ready with JIT
>>> conditions and pc relative instructions relocation.
>>>
>>> I would like to post that in the next few weeks, but it would be
>>> better if the normal tracepoints were in before that.
>>>
>>> Is it a good time to review these patches now?
>>
>> - handle unavailable memory/register in frame unwinding in target
>> independent part, so that we don't have to worry about the
>> unavailable memory in arm backend.
>> I am writing a prototype according to Pedro's thoughts,
>> https://sourceware.org/ml/gdb-patches/2016-02/msg00778.html
>> but it is blocked by a patch related PR 19947,
>> https://sourceware.org/ml/gdb-patches/2016-04/msg00429.html
>> we need an approach to test each unwinder, the discussion is still
>> ongoing.
>>
>
> Thanks for working on that one!
>
> Note however that this only affects the tracing of pseudo registers
> iirc, maybe we can live without this at first and add it as an
> improvement.
>
> Moreover, the required code changes to fix this issue have
> no impact on the tracepoint patches afaik, so I don't see it as a hard
> prerequisite for tracepoints.
I don't think so. If that is done, unwinders in each target don't have
to worry about the unavailable memory/register, your patch 1/4 in this
series is no longer needed.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-04-27 13:57 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 17:45 Antoine Tremblay
2016-01-07 17:45 ` [PATCH 1/4] Teach arm unwinders to terminate gracefully Antoine Tremblay
2016-02-12 14:46 ` Yao Qi
2016-02-24 17:57 ` Antoine Tremblay
2016-02-25 11:44 ` Pedro Alves
2016-02-25 13:15 ` Antoine Tremblay
2016-02-26 9:12 ` Yao Qi
2016-02-26 12:26 ` Antoine Tremblay
2016-02-26 14:25 ` Yao Qi
2016-02-26 20:10 ` Antoine Tremblay
2016-04-06 15:54 ` Yao Qi
2016-04-06 16:30 ` Pedro Alves
2016-04-07 16:33 ` Yao Qi
2016-05-04 16:24 ` Yao Qi
2016-01-07 17:45 ` [PATCH 4/4] Support tracepoints for ARM linux in GDBServer Antoine Tremblay
2016-01-07 17:45 ` [PATCH 3/4] Enable tracing of pseudo-registers on ARM Antoine Tremblay
2016-02-12 15:14 ` Yao Qi
2016-02-12 15:54 ` Marcin Kościelnicki
2016-02-15 10:27 ` Yao Qi
2016-02-15 10:57 ` Pedro Alves
2016-02-15 14:46 ` [PATCH v2] " Antoine Tremblay
2016-02-19 16:33 ` Antoine Tremblay
2016-02-19 19:29 ` [PATCH v3] " Antoine Tremblay
2016-02-19 20:06 ` [PATCH v4] " Antoine Tremblay
2016-02-19 20:22 ` [PATCH v3] " Pedro Alves
2016-02-19 20:32 ` Antoine Tremblay
2016-02-22 11:51 ` Yao Qi
2016-02-22 16:51 ` Antoine Tremblay
2016-02-24 18:11 ` Pedro Alves
2016-02-24 18:21 ` Marcin Kościelnicki
2016-02-24 18:33 ` Pedro Alves
2016-02-24 18:55 ` Antoine Tremblay
2016-02-24 19:02 ` Pedro Alves
2016-02-24 19:02 ` Antoine Tremblay
2016-02-23 19:34 ` Antoine Tremblay
2016-02-24 18:20 ` Pedro Alves
2016-02-24 18:47 ` Antoine Tremblay
2016-02-23 19:41 ` [PATCH v5] " Antoine Tremblay
2016-02-24 19:12 ` Pedro Alves
2016-02-24 19:25 ` Antoine Tremblay
2016-02-25 10:35 ` Yao Qi
2016-02-25 15:33 ` [PATCH v6] " Antoine Tremblay
2016-02-25 17:59 ` Pedro Alves
2016-02-25 18:19 ` Antoine Tremblay
2016-02-26 8:34 ` Yao Qi
2016-02-26 13:00 ` Antoine Tremblay
2016-02-26 13:03 ` [PATCH v7] " Antoine Tremblay
2016-02-26 14:14 ` Yao Qi
2016-02-26 14:57 ` Antoine Tremblay
2016-02-26 14:59 ` [PATCH v8] " Antoine Tremblay
2016-02-26 15:57 ` Yao Qi
2016-02-26 17:45 ` Antoine Tremblay
2016-01-07 17:45 ` [PATCH 2/4] Use the target architecture when encoding tracepoint actions Antoine Tremblay
2016-02-06 20:58 ` Marcin Kościelnicki
2016-02-11 13:02 ` Pedro Alves
2016-02-11 13:21 ` Antoine Tremblay
2016-01-11 12:17 ` [PATCH 0/4] Support tracepoints for ARM linux in GDBServer Yao Qi
2016-01-11 12:56 ` Antoine Tremblay
2016-01-11 13:41 ` Yao Qi
2016-04-26 19:11 ` Antoine Tremblay
2016-04-27 8:00 ` Yao Qi
2016-04-27 12:07 ` Antoine Tremblay
2016-04-27 13:57 ` Yao Qi [this message]
2016-04-27 14:41 ` 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=86a8kff93g.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
/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