From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: GNU Cauldron
Date: Wed, 07 Sep 2016 11:18:00 -0000 [thread overview]
Message-ID: <CAH=s-POUgTHk32_=axsjN5Ja6bdVD6YF6MqoWMkKVsikBLfacQ@mail.gmail.com> (raw)
In-Reply-To: <26ad12ea-64be-073e-2fb4-f28041012501@redhat.com>
On Wed, Sep 7, 2016 at 11:41 AM, Pedro Alves <palves@redhat.com> wrote:
>
> The GDB BoF is right after my talk in the same room, so if we
> end up overflowing, it doesn't look like it'll be a real
> problem.
Yes.
>
> Please let me know which projects those are.
>
- Change software_single_step interface,
1. use regcache instead of frame_info,
2. return a vector of address,
- Support ARM tracepoint and range stepping.
--
Yao (齐尧)
prev parent reply other threads:[~2016-09-07 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 16:11 Yao Qi
2016-08-30 22:06 ` Pedro Alves
2016-09-07 8:15 ` Yao Qi
2016-09-07 10:41 ` Pedro Alves
2016-09-07 11:18 ` Yao Qi [this message]
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='CAH=s-POUgTHk32_=axsjN5Ja6bdVD6YF6MqoWMkKVsikBLfacQ@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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