From: Yao Qi <yao@codesourcery.com>
To: "Gustavo, Luis" <luis_gustavo@mentor.com>
Cc: Tom Tromey <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [RFC stub-side break conditions 3/5] GDB-side changes
Date: Fri, 13 Jan 2012 15:36:00 -0000 [thread overview]
Message-ID: <4F104328.8090908@codesourcery.com> (raw)
In-Reply-To: <4F0C1D39.7050709@mentor.com>
On 01/10/2012 07:12 PM, Luis Machado wrote:
>> I think the patches should include some tests for the new feature.
>
> Yes. I still need to think about those.
>
> I'll probably add a few GDB-side tests for safety, but mostly
> target-side ones like the tracepoint tests.
This patch is about adding evaluating breakpoints' conditions in target
side, so existing test cases for condition breakpoints should be
sufficient for testing. We only need to force gdb to evaluate condition
in target side somewhere in test suite scripts. User can define
target_info in his/her board file to set where to evaluate condition,
host or target.
If we add new test cases, they should be used for both cases (condition
evaluated on host side vs. target side).
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-01-13 14:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:56 Luis Machado
2012-01-06 8:47 ` Eli Zaretskii
2012-01-06 22:38 ` Luis Machado
2012-01-07 7:54 ` Eli Zaretskii
2012-01-12 19:44 ` Pedro Alves
2012-01-12 22:20 ` Tom Tromey
2012-01-13 8:08 ` Eli Zaretskii
2012-01-13 14:33 ` Tom Tromey
2012-01-13 14:44 ` Pedro Alves
2012-01-06 16:23 ` Pedro Alves
2012-01-10 11:14 ` Luis Machado
2012-01-12 19:31 ` Pedro Alves
2012-01-06 21:44 ` Tom Tromey
2012-01-10 14:51 ` Luis Machado
2012-01-13 15:36 ` Yao Qi [this message]
2012-01-13 18:13 ` Pedro Alves
2012-01-14 0:42 ` Yao Qi
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=4F104328.8090908@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.com \
--cc=tromey@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