Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Stray "," in mi-support.exp
Date: Sat, 12 Mar 2005 01:27:00 -0000	[thread overview]
Message-ID: <200503120127.23761.paul@codesourcery.com> (raw)

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

The attached patch removes what appears to be a stray "," in 
testsuite/lib/mi-support.exp

I'd commit as obvious, but I never can be sure with dejagnu.The relevant 
excerpt from testsuite/gdb.log is:

(gdb) ^M
target remote tcp:localhost:2345^M
&"target remote tcp:localhost:2345\n"^M
~"Remote debugging using tcp:localhost:2345\n"^M
~"0x00000000 in ?? ()\n"^M
^done^M
(gdb) ^M

Ok?

Paul

[-- Attachment #2: patch.gdb_mi_exp --]
[-- Type: text/x-diff, Size: 662 bytes --]

Index: gdb/testsuite/lib/mi-support.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/mi-support.exp,v
retrieving revision 1.24
diff -u -p -r1.24 mi-support.exp
--- gdb/testsuite/lib/mi-support.exp	18 Jan 2004 15:23:30 -0000	1.24
+++ gdb/testsuite/lib/mi-support.exp	12 Mar 2005 01:16:39 -0000
@@ -496,7 +496,7 @@ proc mi_gdb_load { arg } {
 	# remote targets
 	send_gdb "target [target_info gdb_protocol] [target_info netport]\n"
 	gdb_expect 60 {
-	    -re "\\^done,.*$mi_gdb_prompt$" {
+	    -re "\\^done.*$mi_gdb_prompt$" {
 	    }
 	    timeout {
 		perror "Unable to connect to remote target"

             reply	other threads:[~2005-03-12  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12  1:27 Paul Brook [this message]
2005-03-13  4:52 ` Daniel Jacobowitz
2005-03-14 15:06   ` Paul Brook
2005-03-14 15:10     ` Daniel Jacobowitz

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=200503120127.23761.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=gdb-patches@sources.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