Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] testsuite: info-shared.exp: Expect leading dot on ppc64's symbols
Date: Wed, 22 Jan 2014 19:18:00 -0000	[thread overview]
Message-ID: <1390418283-11267-1-git-send-email-emachado@linux.vnet.ibm.com> (raw)

Hi,

With this patch, the testcase permits the leading `.' found on ppc64's symbols.
It fixes 10 false unexpected failures on ppc64. Ok?

Thanks,
Edjunior.

gdb/testsuite/
2014-01-22  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* gdb.base/info-shared.exp: Expect leading `.' on ppc64's symbols.

---
 gdb/testsuite/gdb.base/info-shared.exp | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/gdb/testsuite/gdb.base/info-shared.exp b/gdb/testsuite/gdb.base/info-shared.exp
index b7be174..a7cbe1d 100644
--- a/gdb/testsuite/gdb.base/info-shared.exp
+++ b/gdb/testsuite/gdb.base/info-shared.exp
@@ -89,18 +89,18 @@ gdb_breakpoint "foo" allow-pending
 gdb_breakpoint "bar" allow-pending
 
 # Run to the first stop and check that only the first library is loaded.
-gdb_continue_to_breakpoint "library load #1" "stop .*"
+gdb_continue_to_breakpoint "library load #1" "\\.?stop .*"
 check_info_shared "info sharedlibrary #2" 1 0
 
 # Run to the second stop and check that both libraries are loaded.
-gdb_continue_to_breakpoint "library load #2" "stop .*"
+gdb_continue_to_breakpoint "library load #2" "\\.?stop .*"
 check_info_shared "info sharedlibrary #3" 1 1
 
 # Check that the next stop is in foo.
-gdb_continue_to_breakpoint "library function #1" "foo .*"
+gdb_continue_to_breakpoint "library function #1" "\\.?foo .*"
 
 # Check that the next stop is in bar.
-gdb_continue_to_breakpoint "library function #2" "bar .*"
+gdb_continue_to_breakpoint "library function #2" "\\.?bar .*"
 
 # Restart the inferior and make sure there are no breakpoint reset
 # errors.  These can happen with the probes-based runtime linker
@@ -124,23 +124,23 @@ gdb_test_multiple "" $test {
 check_info_shared "info sharedlibrary #4" 0 0
 
 # Run to the first stop and check that only the first library is loaded.
-gdb_continue_to_breakpoint "library load #3" "stop .*"
+gdb_continue_to_breakpoint "library load #3" "\\.?stop .*"
 check_info_shared "info sharedlibrary #5" 1 0
 
 # Run to the second stop and check that both libraries are loaded.
-gdb_continue_to_breakpoint "library load #4" "stop .*"
+gdb_continue_to_breakpoint "library load #4" "\\.?stop .*"
 check_info_shared "info sharedlibrary #6" 1 1
 
 # Check that the next stop is in foo.
-gdb_continue_to_breakpoint "library function #3" "foo .*"
+gdb_continue_to_breakpoint "library function #3" "\\.?foo .*"
 
 # Check that the next stop is in bar.
-gdb_continue_to_breakpoint "library function #4" "bar .*"
+gdb_continue_to_breakpoint "library function #4" "\\.?bar .*"
 
 # Run to the next stop and check that the first library has been unloaded.
-gdb_continue_to_breakpoint "library unload #1" "stop .*"
+gdb_continue_to_breakpoint "library unload #1" "\\.?stop .*"
 check_info_shared "info sharedlibrary #7" 0 1
 
 # Run to the last stop and check that both libraries are gone.
-gdb_continue_to_breakpoint "library unload #2" "stop .*"
+gdb_continue_to_breakpoint "library unload #2" "\\.?stop .*"
 check_info_shared "info sharedlibrary #8" 0 0
-- 
1.8.1.4


             reply	other threads:[~2014-01-22 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 19:18 Edjunior Barbosa Machado [this message]
2014-01-22 19:42 ` Sergio Durigan Junior
2014-01-22 20:52   ` Sergio Durigan Junior
2014-01-28 15:59 ` [PATCH] testsuite: info-shared.exp: Expect leading.on " Ulrich Weigand
2014-01-28 16:36   ` Joel Brobecker
2014-01-28 17:39     ` Edjunior Barbosa Machado
2014-01-28 19:23     ` Sergio Durigan Junior

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=1390418283-11267-1-git-send-email-emachado@linux.vnet.ibm.com \
    --to=emachado@linux.vnet.ibm.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