Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 1/2] Fixes to gdb.base/dump.exp: get value from address instead of name
Date: Wed, 22 Jun 2011 15:45:00 -0000	[thread overview]
Message-ID: <m339j1kh00.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4E00794D.708@codesourcery.com> (Yao Qi's message of "Tue, 21 Jun	2011 18:58:21 +0800")

>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> IMO, the intention of tests in this gdb session is to test that "gdb is
Yao> able to load these dump files, and read the correct memory contents from
Yao> them", so it doesn't matter too much that gdb get them via name or
Yao> address.  I think the semantics of this part of tests is not changed.

I agree.

Yao> +proc capture_value_with_type { expression } {

I don't fully understand this proc.  Some comments would help.

Yao> +	    if [regexp { \(.*\).*[0-9]+} $expect_out(0,string) output_string] {

Is [0-9]+ really correct?
I would have thought the results would be in hex.
This would be a good spot for a comment describing the expected output.

Yao> +		pass "$test $output_string"
Yao> +	    } else {
Yao> +		fail "$test unable to match regexp"
Yao> +	    }

Passes and fails should use the same text.

Tom


  reply	other threads:[~2011-06-22 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 10:42 [patch 0/2] Fixes to gdb.base/dump.exp Yao Qi
2011-06-21 10:58 ` [patch 1/2] Fixes to gdb.base/dump.exp: get value from address instead of name Yao Qi
2011-06-22 15:45   ` Tom Tromey [this message]
2011-06-23 10:28     ` Yao Qi
2011-07-01 14:16       ` Yao Qi
2011-07-01 14:23         ` Tom Tromey
2011-07-01 16:51           ` [committed] " Yao Qi
2011-06-21 11:05 ` [patch 2/2] Fixes to gdb.base/dump.exp: Combine dump and restore in a single session 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=m339j1kh00.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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