Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: GDB MI Reverse Commands added [3 of 3]
Date: Wed, 02 Sep 2009 08:23:00 -0000	[thread overview]
Message-ID: <h7la0n$uvt$1@ger.gmane.org> (raw)
In-Reply-To: <00d001ca265a$ddd0c800$99725800$@com>

Jakob Engblom wrote:

> Final part: the test suite for gdb-MI reverse debugging commands. Attached as a
> file, to be put in [gdb]/src/gdb/testsuite/gdb.mi/

The file should be called mi-reverse.exp, I think, because mi2- files are supposed to test
that whatever was once announced as MI2 is not broken. And this is new development. Likewise,

        set MIFLAGS "-i=mi2"

should be:

        set MIFLAGS "-i=mi"

Also, I would appreciate if this:

    # Test exec-reverse-next
    # FIXME: Why does it take 2 next commands to get back to the
    #        previous line?

were somehow addressed. I am not familiar with details of reverse behaviour, so I
did not even try to check that the tested commands and locations, etc, are right.

This is OK with the above fixes and the fixes asked for by Michael.

Thanks,
Volodya



  parent reply	other threads:[~2009-09-02  8:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 15:10 Jakob Engblom
2009-08-27  1:43 ` Michael Snyder
2009-08-31 13:13   ` Jakob Engblom
2009-09-01 12:48     ` Jakob Engblom
2009-09-01 17:36       ` Tom Tromey
2009-09-07  1:18       ` Michael Snyder
2009-09-07  7:10         ` Jakob Engblom
2009-09-07 18:09           ` Joel Brobecker
2009-09-08  7:11             ` Jakob Engblom
2009-09-02  8:23 ` Vladimir Prus [this message]
2009-09-03 18:44   ` Jakob Engblom
2009-09-03 20:13     ` Michael Snyder
2009-09-07  1:44     ` Hui Zhu
2009-12-15 19:43     ` Michael Snyder
2009-12-16  9:59       ` Vladimir Prus
2009-12-15 19:42 ` Michael Snyder
2009-12-16  8:06   ` Vladimir Prus
2009-12-16  8:48     ` Jakob Engblom
2009-12-16 10:05       ` Vladimir Prus
2010-02-12 21:39         ` Michael Snyder

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='h7la0n$uvt$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.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