From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>, Yao Qi <yao@codesourcery.com>
Subject: Re: [patch] Run tests in gdb.reverse
Date: Mon, 07 Nov 2011 15:08:00 -0000 [thread overview]
Message-ID: <201111071507.58347.pedro@codesourcery.com> (raw)
In-Reply-To: <m3k47cnftn.fsf@fleche.redhat.com>
On Monday 07 November 2011 14:54:28, Tom Tromey wrote:
> >>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
>
> Yao> During reviewing "arm reverse debugging" patch, we realize that tests in
> Yao> gdb.reverse are not run in common regression test unless we set some
> Yao> variables in board file.
>
> Yao> This patch is to convert variable checking in each reverse test case to
> Yao> a proc return value checking, so that gdb.reverse tests will be run on
> Yao> targets that support reverse debugging.
>
> Thanks for doing this.
>
> Yao> +proc support_process_record {} {
> Yao> +
> Yao> + if { [istarget "x86_64-*-linux*"] || [istarget "i\[34567\]86-*-linux*"] } {
>
> It seems to me that both of the new procs should include the old check
> using target_info as well, just in case. This will avoid breaking
> anybody's existing setup.
Yes, we need to be able to run the reverse tests against
remote targets that support reverse debugging themselves.
E.g., simulators. Those can do reverse debugging on their own,
target record is not involved. Can we make predicates supportS_FOO
(add an S)? support_FOO reads as an action to me.
--
Pedro Alves
next prev parent reply other threads:[~2011-11-07 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 17:36 Yao Qi
2011-11-07 14:39 ` Joel Brobecker
2011-11-07 14:55 ` Tom Tromey
2011-11-07 15:08 ` Pedro Alves [this message]
2011-11-08 8:15 ` 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=201111071507.58347.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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