From: Fred Fish <fnf@ninemoons.com>
To: gdb-patches@sources.redhat.com
Cc: fnf@redhat.com
Subject: [RFA] Fix testsuite gdb.base/bang.exp to work with remote targets
Date: Mon, 02 Feb 2004 20:26:00 -0000 [thread overview]
Message-ID: <200402021326.08063.fnf@ninemoons.com> (raw)
When using a remote target, like SID, you have to "continue" after
a "gdb_load", not "run". Add support for this case.
2004-02-02 Fred Fish <fnf@redhat.com>
* gdb.base/bang.exp: Handling continuing on remote targets after a
load.
Index: gdb.base/bang.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bang.exp,v
retrieving revision 1.1
diff -u -p -r1.1 bang.exp
--- gdb.base/bang.exp 24 Jun 2003 22:04:06 -0000 1.1
+++ gdb.base/bang.exp 2 Feb 2004 20:20:04 -0000
@@ -1,4 +1,4 @@
-# Copyright 2003 Free Software Foundation, Inc.
+# Copyright 2003, 2004 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
@@ -35,7 +35,10 @@ gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
# Verify that we can run the program and that it terminates normally.
-gdb_test "run" \
- ".*Program exited normally\." \
- "run program"
+# For remote targets we simply continue after loading.
+if [target_info exists use_gdb_stub] {
+ gdb_test "continue" ".*Program exited normally\." "run program"
+} else {
+ gdb_test "run" ".*Program exited normally\." "run program"
+}
next reply other threads:[~2004-02-02 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 20:26 Fred Fish [this message]
2004-02-02 20:32 ` Daniel Jacobowitz
2004-02-02 20:56 ` Fred Fish
2004-02-02 21:01 ` Daniel Jacobowitz
2004-02-02 21:17 ` Fred Fish
2004-02-02 21:23 ` 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=200402021326.08063.fnf@ninemoons.com \
--to=fnf@ninemoons.com \
--cc=fnf@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