From: Luis Gustavo <luis_gustavo@mentor.com>
Cc: gdb-patches@sourceware.org
Subject: [ping] [rfc target-side break conditions 0/5 v2] General info
Date: Mon, 06 Feb 2012 13:33:00 -0000 [thread overview]
Message-ID: <4F2FD659.5070708@mentor.com> (raw)
In-Reply-To: <4F2309F1.1020703@mentor.com>
Ping this updated series.
On 01/27/2012 06:32 PM, Luis Gustavo wrote:
> Hi,
>
> This is an updated series of patches to implement target-side breakpoint
> condition evaluation.
>
> Most of the changes are in part 1, 3 and 5. The other parts had only
> minor changes.
>
> The current testsuite seems to be a good exercise for this feature when
> ran in gdbserver mode. I can provide additional tests if required.
>
> Part 1: Documentation bits
> Part 2: Protocol and feature changes
> Part 3: GDB-specific changes
> Part 4: GDBServer tracepoint/agent expression common code cleanup
> Part 5: GDBServer breakpoint condition evaluation enablement
>
> Luis
>
next prev parent reply other threads:[~2012-02-06 13:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:33 Luis Gustavo
2012-02-06 13:33 ` Luis Gustavo [this message]
2012-02-07 21:32 ` Stan Shebs
2012-02-08 23:05 ` Luis Gustavo
2012-02-24 15:28 ` Luis Gustavo
2012-02-25 15:40 ` General regressions in gdbserver mode [Re: [rfc target-side break conditions 0/5 v2] General info] Jan Kratochvil
2012-02-25 15:57 ` Luis Gustavo
2012-02-25 17:19 ` Jan Kratochvil
2012-02-25 18:25 ` Luis Gustavo
2012-02-25 19:40 ` Luis Gustavo
2012-02-25 19:41 ` Jan Kratochvil
2012-02-25 20:08 ` Luis Gustavo
2012-02-26 22:57 ` Regressions in gdbserver mode #2 [Re: General regressions in gdbserver mode] Jan Kratochvil
2012-02-26 23:09 ` Luis Gustavo
2012-02-28 16:19 ` Jan Kratochvil
2012-02-27 4:46 ` Luis Gustavo
2012-02-27 5:55 ` Jan Kratochvil
2012-02-27 16:23 ` Luis Gustavo
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=4F2FD659.5070708@mentor.com \
--to=luis_gustavo@mentor.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