Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Some issue with reverse testsuite
Date: Mon, 29 Jun 2009 18:29:00 -0000	[thread overview]
Message-ID: <4A490779.9090006@vmware.com> (raw)
In-Reply-To: <daef60380906290004n29312375t412e38c80efba03c@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

Hui Zhu wrote:
> Hi Michael,
> 
> I try the reverse testsuite in cvs-head, what I got is:

[...]

> It looks like gdb do nothing.  Are you sure it works OK?

You need to use a board description file to enable them.
Oh damn -- I don't know where this stuff is documented.

Guys -- how do we usually initiate a new maintainer into
the mysteries of dejagnu?

Hui -- let me tell you the easy (and wrong) way to do it,
just to avoid complexity.  Copy the attached file into
/usr/share/dejagnu/baseboards (you'll need to be root).

Then add "--target_board=precord" to your RUNTESTFLAGS,
eg. like this:

   make check RUNTESTFLAGS="step-reverse.exp --target_board=precord"


[-- Attachment #2: precord.exp --]
[-- Type: text/plain, Size: 161 bytes --]

# Testing programs using process record/replay (precord)

load_base_board_description "unix"

set_board_info gdb,can_reverse 1
set_board_info gdb,use_precord 1


  reply	other threads:[~2009-06-29 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29  7:05 Hui Zhu
2009-06-29 18:29 ` Michael Snyder [this message]
2009-06-29 18:36   ` Daniel Jacobowitz
2009-06-29 21:52   ` Hui Zhu

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=4A490779.9090006@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=teawater@gmail.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