From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add autoload-breakpoints [0/7]
Date: Mon, 19 Mar 2012 04:48:00 -0000 [thread overview]
Message-ID: <4F66BA7D.7050500@codesourcery.com> (raw)
In-Reply-To: <4F6450AF.5010609@mentor.com>
On 03/17/2012 04:51 PM, Hui Zhu wrote:
> Hi,
>
> There are patches to make GDB support autoload-breakpoints.
For avoid of doubt, here is a high level description of these patches:
Prior to GDB connects to remote stub, some breakpoints might have been
already set in target, either by a prior GDB session or by the program
itself through some special system API. When GDB connects to target, it
should handle these existing breakpoints from remote stub. We call
these breakpoints as "auotload breakpoints".
> It is:
> 1. it is set by the remote stub.
> 2. The remote stub can control autoload-breakpoints any time even if GDB
> is just control the inferior.
The other use case we want to support in GDB is that inferior may
delete/clear breakpoints on its own, and remote stub gets GDB notified,
and GDB can take some actions accordingly. We believe such reliable
report is useful to GDB, and generalize it, called "ReportAsync".
The connection between "ReportAsync" and "autoload breakpoint" is when
inferior/stub delete breakpoints, sends async report to GDB about
removed breakpoints.
--
Yao (é½å°§)
prev parent reply other threads:[~2012-03-19 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 8:52 Hui Zhu
2012-03-17 11:13 ` [OT] DKIM/DomainKeys headers in messages from this list Eli Zaretskii
2012-03-17 13:42 ` Hui Zhu
2012-03-17 14:43 ` Eli Zaretskii
2012-03-18 16:34 ` Jan Kratochvil
2012-03-18 17:02 ` Eli Zaretskii
2012-03-19 4:48 ` 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=4F66BA7D.7050500@codesourcery.com \
--to=yao@codesourcery.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