From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>
Subject: [RFA] Fix "show convenience" test
Date: Wed, 16 Sep 2009 00:32:00 -0000 [thread overview]
Message-ID: <200909152132.15317.sergiodj@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 1093 bytes --]
Hi guys,
This is a simple one. After running GDB's testsuite, I saw that one of the
gdb.base/default.exp's tests was not passing. It tested the output of the
"show convenience" command.
After a little investigation, it seems that:
http://sourceware.org/ml/gdb-patches/2009-02/msg00165.html
Is the responsible for this, since this patch was creating an internal
convenience variable ($_siginfo) which appears in the "show convenience"
command, while the original test expects to receive a warning saying that no
convenience variable is created at the moment. If I understood the patch
correctly, the $_siginfo will be always created and therefore the test should
now expect "$_siginfo = void" instead of this warning. Am I missing
something?
Regards,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil
gdb/testsuite/ChangeLog:
2009-09-15 Sergio Durigan Junior <sergiosdj@gmail.com>
* gdb.base/default.exp: Updated the "show convenience" test
in order to accept the new output.
[-- Attachment #2: show-convenience.patch --]
[-- Type: text/x-patch, Size: 900 bytes --]
diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp
index a223982..a0cb11e 100644
--- a/gdb/testsuite/gdb.base/default.exp
+++ b/gdb/testsuite/gdb.base/default.exp
@@ -598,7 +598,7 @@ gdb_test "show complaints" "Max number of complaints about incorrect symbols is
#test show confirm
gdb_test "show confirm" "Whether to confirm potentially dangerous operations is o\[a-z\]*." "show confirm"
#test show convenience
-gdb_test "show convenience" "No debugger convenience variables now defined.(\[^\r\n\]*\[\r\n\])+Convenience variables have names starting with \".\";(\[^\r\n\]*\[\r\n\])+use \"set\" as in \"set .foo = 5\" to define them." "show convenience"
+gdb_test "show convenience" "\\\$_siginfo = void" "show convenience"
#test show directories
gdb_test "show directories" "Source directories searched: .cdir\[:;\].cwd" "show directories"
#test show editing
next reply other threads:[~2009-09-16 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 0:32 Sérgio Durigan Júnior [this message]
2009-09-16 13:16 ` Pedro Alves
2009-09-16 17:08 ` Eli Zaretskii
2009-09-17 16:37 ` Paul Pluzhnikov
2009-09-17 17:26 ` Eli Zaretskii
2009-09-17 17:57 ` Paul Pluzhnikov
2009-09-17 18:16 ` Pedro Alves
2009-09-17 18:29 ` Paul Pluzhnikov
2009-09-17 19:25 ` Joseph S. Myers
2009-09-17 19:52 ` Pedro Alves
2009-09-17 18:26 ` Eli Zaretskii
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=200909152132.15317.sergiodj@linux.vnet.ibm.com \
--to=sergiodj@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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