Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: <gdb@sourceware.org>
Subject: gdb reverse execution: how to actually run tests for it?
Date: Mon, 17 Aug 2009 07:42:00 -0000	[thread overview]
Message-ID: <002001ca1f0e$4c9b74a0$e5d25de0$@com> (raw)

I am trying to finally implement the reverse ability for MI commands, but
creating and testing the tests is looking challenging. The fundamental issue is
that it seems that I cannot get the regular reverse tests to run, to know how to
properly code the reverse tests for reverse MI. 

When I run

$ make check RUNTESTFLAGS="gdb.reverse/*.exp"

There is a flurry of activity ending in this:

---
                === gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific
interface file.
Running ../../../src/gdb/testsuite/gdb.reverse/solib-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/step-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/until-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/break-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/finish-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/machinestate.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/consecutive-reverse.exp ...
Running ../../../src/gdb/testsuite/gdb.reverse/watch-reverse.exp ...

                === gdb Summary ===

/home/jakob/gdb7/gdb-host-revpatched/gdb/testsuite/../../gdb/gdb version
6.8.50.20090814-cvs -nw -nx

make[3]: Leaving directory `/home/jakob/gdb7/gdb-host-revpatched/gdb/testsuite'
make[2]: Leaving directory `/home/jakob/gdb7/gdb-host-revpatched/gdb'
make[1]: Nothing to be done for `check-target'.
make[1]: Leaving directory `/home/jakob/gdb7/gdb-host-revpatched'
---

Which seems to indicate that no tests were actually run. This is a 6.8.50 branch
that I checked out of cvs late last week. 

What is required to actually run the reverse tests? Do I need to build my gdb in
any special way?

I suspect that this line the test scripts is the cause of the premature exit
from the tests:

---
if ![target_info exists gdb,can_reverse] {
    return
}
---

So how do I make gdb realize that it can indeed reverse itself?

Best regards,

/jakob

_______________________________________________________

Jakob Engblom, PhD, Technical Marketing Manager

Virtutech                   Direct: +46 8 690 07 47   
Drottningholmsvägen 22      Mobile: +46 709 242 646  
11243 Stockholm             Web:    www.virtutech.com 
Sweden
________________________________________________________
  



             reply	other threads:[~2009-08-17  7:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17  7:42 Jakob Engblom [this message]
2009-08-17  7:58 ` Hui Zhu
2009-08-17 11:33   ` Jakob Engblom
2009-08-17 11:50   ` Jakob Engblom
2009-08-17 11:55     ` Pedro Alves
2009-08-17 15:31       ` Pedro Alves
2009-08-17 15:52         ` Hui Zhu
2009-08-20 17:10           ` Pedro Alves
2009-08-19  7:34         ` Jakob Engblom
2009-08-17 18:24       ` Michael Snyder
2009-08-17 20:08         ` Jakob Engblom
2009-08-17 22:44           ` Michael Snyder
2009-08-19  7:24             ` Jakob Engblom
2009-08-19  8:58             ` Simics & reverse execution Jakob Engblom
2009-08-19 12:29               ` Hui Zhu
2009-08-19 20:03                 ` Jakob Engblom
2009-08-19 20:29                   ` Michael Snyder
2009-08-19 20:44                     ` Daniel Jacobowitz
2009-08-19 21:09                     ` Pedro Alves
2009-08-20  6:54                       ` Jakob Engblom
2009-08-20 15:03                         ` Pedro Alves
2009-08-27  4:44               ` Michael Snyder
2009-08-27  8:17                 ` Jakob Engblom
2009-08-28 11:04                   ` Michael Snyder
2009-08-28 15:17                 ` Greg Law
2009-08-31 13:22                   ` Jakob Engblom
2009-08-31 16:34                     ` Greg Law
2009-09-01  6:37                       ` Jakob Engblom
2009-09-01 13:49                         ` Greg Law
2009-09-03 19:16                           ` Jakob Engblom
2009-09-04 12:44                             ` Greg Law
2009-09-07  7:16                               ` Jakob Engblom
2009-09-07  8:13                                 ` Greg Law
2009-09-07  8:24                                   ` Jakob Engblom
2009-09-07 12:06                                     ` Greg Law
2009-09-08  7:21                                       ` Jakob Engblom
2009-09-08 12:08                                         ` Greg Law
2009-09-08 13:02                                           ` Jakob Engblom
2009-09-08 19:11                                             ` Greg Law
2009-09-14  8:26                                               ` Jakob Engblom
2009-09-17  3:07                                                 ` Michael Snyder
2009-08-19  7:24       ` gdb reverse execution: how to actually run tests for it? Jakob Engblom
2009-08-19 15:28         ` Pedro Alves
2009-08-19 16:37           ` Tom Tromey
2009-08-20 13:10             ` Jakob Engblom
2009-08-20 14:50               ` Daniel Jacobowitz
2009-08-20 20:27               ` Michael Snyder
2009-08-20  6:53           ` 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='002001ca1f0e$4c9b74a0$e5d25de0$@com' \
    --to=jakob@virtutech.com \
    --cc=gdb@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