public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: jkratoch@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-jankratochvil-watchpoint3: Fix testcase after the DW_AT_linkage_name-following upstream change.
Date: Sun, 03 Jul 2011 14:41:00 -0000	[thread overview]
Message-ID: <20110703144143.29800.qmail@sourceware.org> (raw)

The branch, archer-jankratochvil-watchpoint3 has been updated
       via  0a258bc6362d53cf8dca76d849e6e7dbe55173ec (commit)
      from  73cd95e5927db9010f9bb387ab27737eb8ac7fb9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 0a258bc6362d53cf8dca76d849e6e7dbe55173ec
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Sun Jul 3 16:41:15 2011 +0200

    Fix testcase after the DW_AT_linkage_name-following upstream change.

-----------------------------------------------------------------------

Summary of changes:
 gdb/testsuite/gdb.multi/watchpoint-multi.exp |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

First 500 lines of diff:
diff --git a/gdb/testsuite/gdb.multi/watchpoint-multi.exp b/gdb/testsuite/gdb.multi/watchpoint-multi.exp
index 97fa6cd..21d6a31 100644
--- a/gdb/testsuite/gdb.multi/watchpoint-multi.exp
+++ b/gdb/testsuite/gdb.multi/watchpoint-multi.exp
@@ -89,7 +89,7 @@ gdb_test_multiple "continue" $test {
 	setup_kfail breakpoints/12312 *-*-*
 	pass $test
     }
-    -re "Hardware access \\(read/write\\) watchpoint \[0-9\]+: c\r\n\r\nValue = 3\r\n(.* in )?__nptl_death_event .*\r\n$gdb_prompt $" {
+    -re "Hardware access \\(read/write\\) watchpoint \[0-9\]+: c\r\n\r\nValue = 3\r\n(.* in )?(\\*__GI_)?__nptl_death_event .*\r\n$gdb_prompt $" {
 	setup_kfail breakpoints/12312 *-*-*
 	fail $test
     }
@@ -105,7 +105,7 @@ gdb_test_multiple "continue" $test {
 	setup_kfail breakpoints/12312 *-*-*
 	pass $test
     }
-    -re "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b\r\n\r\nValue = 2\r\n(.* in )?__nptl_death_event .*\r\n$gdb_prompt $" {
+    -re "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b\r\n\r\nValue = 2\r\n(.* in )?(\\*__GI_)?__nptl_death_event .*\r\n$gdb_prompt $" {
 	setup_kfail breakpoints/12312 *-*-*
 	fail $test
     }


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2011-07-03 14:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110703144143.29800.qmail@sourceware.org \
    --to=jkratoch@sourceware.org \
    --cc=archer-commits@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).