Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit#2] [testsuite patch]#2 Fix PR threads/19422 regression + Guile regression [Re: [PATCH+doc] Fix PR threads/19422 - show which thread caused stop]
Date: Fri, 22 Jan 2016 20:51:00 -0000	[thread overview]
Message-ID: <20160122205123.GA14872@host1.jankratochvil.net> (raw)
In-Reply-To: <56A294BE.60805@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

On Fri, 22 Jan 2016 21:44:46 +0100, Pedro Alves wrote:
> Looks like you forgot to amend before pushing though -- the version
> checked in still had "Thread 1".

That was a typo/thinko, sorry.


Jan

[-- Attachment #2: Type: message/rfc822, Size: 1823 bytes --]

From: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: [PATCH] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number
Date: Fri, 22 Jan 2016 21:49:38 +0100

Pedro Alves:
Looks like you forgot to amend before pushing though -- the version
checked in still had "Thread 1".

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
	number.
---
 gdb/testsuite/ChangeLog            | 7 +++++++
 gdb/testsuite/gdb.gdb/selftest.exp | 2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5e99adf..8f7dc6d 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,4 +1,11 @@
 2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
+	    Pedro Alves  <palves@redhat.com>
+
+	Fix testsuite compatibility with Guile.
+	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
+	number.
+
+2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
 
 	Fix testsuite compatibility with Guile.
 	* gdb.gdb/selftest.exp (send ^C to child process): Accept also Thread.
diff --git a/gdb/testsuite/gdb.gdb/selftest.exp b/gdb/testsuite/gdb.gdb/selftest.exp
index 3d98a0c..969797a 100644
--- a/gdb/testsuite/gdb.gdb/selftest.exp
+++ b/gdb/testsuite/gdb.gdb/selftest.exp
@@ -438,7 +438,7 @@ proc test_with_self { executable } {
 	send_gdb "\003"
 	# "Thread 1" is displayed iff Guile support is linked in.
 	gdb_expect {
-	    -re "(Thread 1 .*|Program) received signal SIGINT.*$gdb_prompt $" {
+	    -re "(Thread .*|Program) received signal SIGINT.*$gdb_prompt $" {
 		pass "$description"
 	    }
 	    -re ".*$gdb_prompt $" {
-- 
2.5.0

  reply	other threads:[~2016-01-22 20:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 23:30 [PATCH] Fix PR threads/19422 - show which thread caused stop Pedro Alves
2016-01-14 14:08 ` [PATCH+doc] " Pedro Alves
2016-01-14 16:36   ` Eli Zaretskii
2016-01-14 17:12     ` Pedro Alves
2016-01-14 18:25       ` Eli Zaretskii
2016-01-14 19:00         ` Pedro Alves
2016-01-14 19:06           ` Eli Zaretskii
2016-01-18 15:17             ` Pedro Alves
2016-01-22 16:44   ` Jan Kratochvil
2016-01-22 16:55     ` Pedro Alves
2016-01-22 16:56       ` Jan Kratochvil
2016-01-22 17:30   ` [testsuite patch] Fix PR threads/19422 regression + Guile regression [Re: [PATCH+doc] Fix PR threads/19422 - show which thread caused stop] Jan Kratochvil
2016-01-22 17:31     ` [testsuite patch]#2 " Jan Kratochvil
2016-01-22 18:18       ` [testsuite patch]#3 " Jan Kratochvil
2016-01-22 18:37       ` [testsuite patch]#2 " Pedro Alves
2016-01-22 20:05         ` Jan Kratochvil
2016-01-22 20:11           ` Pedro Alves
2016-01-22 20:17             ` Pedro Alves
2016-01-22 20:25               ` [commit] " Jan Kratochvil
2016-01-22 20:44                 ` Pedro Alves
2016-01-22 20:51                   ` Jan Kratochvil [this message]
2016-01-22 20:53                     ` [commit#2] " Pedro Alves
2016-01-14 16:04 ` [PATCH] Fix PR threads/19422 - show which thread caused stop Yao Qi
2016-01-18 15:24   ` Pedro Alves

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=20160122205123.GA14872@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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