Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/RFC] testsuite: gdb_run_cmd tweak
Date: Mon, 18 Apr 2005 19:51:00 -0000	[thread overview]
Message-ID: <42640FA7.9090406@redhat.com> (raw)

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

This just adds a regular expression to prevent gdb_run_cmd
from choking on the msg that gdb emits when it detects that
the file has changed and re-reads the symbols.

I honestly don't remember the circumstances that caused me
to add this -- it's been sitting in my sandbox for a while.
Thought it would be better to offer it up than to throw it
away...


[-- Attachment #2: lib --]
[-- Type: text/plain, Size: 672 bytes --]

2005-04-18  Michael Snyder  <msnyder@redhat.com>

	* lib/gdb.exp (gdb_run_cmd): Keep going past "executable has 
	changed" msg.

Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.61
diff -p -r1.61 gdb.exp
*** lib/gdb.exp	14 Apr 2005 19:06:19 -0000	1.61
--- lib/gdb.exp	18 Apr 2005 19:42:38 -0000
*************** proc gdb_run_cmd {args} {
*** 258,263 ****
--- 258,266 ----
  	    send_gdb "y\n"
  	    exp_continue
  	}
+ 	-re ".* has changed; re-reading symbols\[^\r\n\]*\[\r\n\]*" {
+ 	    exp_continue
+ 	}
  	-re "Starting program: \[^\r\n\]*" {}
      }
  }

             reply	other threads:[~2005-04-18 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 19:51 Michael Snyder [this message]
2005-04-18 21:42 ` Stan Shebs
2005-04-18 21:46   ` Michael Snyder
2005-04-18 22:09     ` Stan Shebs
2005-04-18 23:00       ` Michael Snyder
2005-04-19 15:49         ` Paul Gilliam
2005-04-19 16:36           ` Daniel Jacobowitz
2005-04-18 21:54 ` Daniel Jacobowitz
2005-04-18 22:05   ` Michael Snyder

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=42640FA7.9090406@redhat.com \
    --to=msnyder@redhat.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