From: Hui Zhu <teawater@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Hui Zhu <hui_zhu@mentor.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Target-defined breakpoints [3/9] notification async
Date: Wed, 24 Oct 2012 17:23:00 -0000 [thread overview]
Message-ID: <CANFwon08kvG1Mb=vpe+jNW2CNjGyWkt=5weSkOohcObwdiKLOg@mail.gmail.com> (raw)
In-Reply-To: <50881981.7070308@codesourcery.com>
On Thu, Oct 25, 2012 at 12:38 AM, Yao Qi <yao@codesourcery.com> wrote:
> On 10/24/2012 11:03 PM, Hui Zhu wrote:
>>
>> This patch is the extend for the notification function.
>> Current notification function cannot handle the packet when GDB doesn't
>> want to send or receive packet from the remote target.
>> This patch do the extend make GDB can handle the notification even if it
>> doesn't send or receive packet.
>
>
> Looks we have two set of 'async notification' stuff here :) I am trying to
> set up an infrastructure of 'async notification' in gdb, so that other
> components can use it. Patches are here,
>
> http://sourceware.org/ml/gdb-patches/2012-10/msg00404.html
> [RFC 0/7 V3]A general notification in GDB RSP
>
> It is general, not specific to any notifications, and scalable. We've
> probably have two internal cases of using it, 'trace status change' and
> 'stub/probe status change', so "Target-defined breakpoint" can use it easily
> as well.
>
> Do you mind if I suggest maintainers to review my 'async notification'
> patches first? Once they go in, we can rebase your patch on top of it. I
> am sure your patch will be shorter dramatically then. WDYT? Or if you find
> my 'async notification' doesn't meet your needs, let me know.
>
> --
> Yao
I don't mind change my patch according to your change if you can check in.
PS. I think target-defind xxx patches still have some work (format
and handler, please read the 0/9) not done. So please don't worry
about it.
Best,
Hui
prev parent reply other threads:[~2012-10-24 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 15:04 Hui Zhu
2012-10-24 16:38 ` Yao Qi
2012-10-24 17:23 ` Hui Zhu [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='CANFwon08kvG1Mb=vpe+jNW2CNjGyWkt=5weSkOohcObwdiKLOg@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=yao@codesourcery.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