Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: "dje\@google.com" <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [commit] Update help.exp
Date: Mon, 10 Sep 2012 17:29:00 -0000	[thread overview]
Message-ID: <871ui9eqhp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <503DF8D2.8070807@arm.com> (Yufeng Zhang's message of "Wed, 29	Aug 2012 12:11:14 +0100")

>>>>> ">" == Yufeng Zhang <Yufeng.Zhang@arm.com> writes:

>> help.exp still fails with --without-python.  "Convenience functions
>> are defined via the Python API" is printed only when HAVE_PYTHON is
>> defined (see
>> http://sourceware.org/ml/gdb-patches/2012-08/msg00342.html).

I ran into this too.

Here's my proposed fix.
Tested on x86-64 F16, both with and without Python enabled.

Tom

b/gdb/testsuite/ChangeLog:
2012-09-10  Tom Tromey  <tromey@redhat.com>

	* gdb.base/help.exp: Conditionally allow Python output.

diff --git a/gdb/testsuite/gdb.base/help.exp b/gdb/testsuite/gdb.base/help.exp
index 7fffd00..3270565 100644
--- a/gdb/testsuite/gdb.base/help.exp
+++ b/gdb/testsuite/gdb.base/help.exp
@@ -517,7 +517,7 @@ gdb_test "help show complaints" "Show max number of complaints about incorrect s
 # test help show confirm
 gdb_test "help show confirm" "Show whether to confirm potentially dangerous operations\." "help show confirm"
 # test help show convenience
-gdb_test "help show convenience" "Debugger convenience \\(\"\\\$foo\"\\) variables and functions\.\[\r\n\]+Convenience variables are created when you assign them values;\[\r\n\]+thus, \"set \\\$foo=1\" gives \"\\\$foo\" the value 1\.  Values may be any type\.\[\r\n\]+A few convenience variables are given values automatically:\[\r\n\]+\"\\\$_\"holds the last address examined with \"x\" or \"info lines\",\[\r\n\]+\"\\\$__\" holds the contents of the last address examined with \"x\"\.\[\r\n\]+Convenience functions are defined via the Python API\." "help show convenience"
+gdb_test "help show convenience" "Debugger convenience \\(\"\\\$foo\"\\) variables and functions\.\[\r\n\]+Convenience variables are created when you assign them values;\[\r\n\]+thus, \"set \\\$foo=1\" gives \"\\\$foo\" the value 1\.  Values may be any type\.\[\r\n\]+A few convenience variables are given values automatically:\[\r\n\]+\"\\\$_\"holds the last address examined with \"x\" or \"info lines\",\[\r\n\]+\"\\\$__\" holds the contents of the last address examined with \"x\"\.\[\r\n\]+(Convenience functions are defined via the Python API\.)?" "help show convenience"
 # test help show directories
 gdb_test "help show directories" "Show the search path for finding source files\.\[\r\n\]+\\\$cwd in the path means the current working directory\.\[\r\n\]+\\\$cdir in the path means the compilation directory of the source file\..*" "help show directories"
 # test help show editing


  reply	other threads:[~2012-09-10 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 21:13 dje
2012-08-29 11:11 ` Yufeng Zhang
2012-09-10 17:29   ` Tom Tromey [this message]
2012-09-10 17:41     ` Doug Evans
2012-09-10 18:01       ` Tom Tromey
2012-09-11  0:22         ` dje
2012-09-11 15:39           ` Tom Tromey
2012-09-11 16:31           ` Yufeng Zhang

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=871ui9eqhp.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Yufeng.Zhang@arm.com \
    --cc=dje@google.com \
    --cc=gdb-patches@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