Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: FYI: clean up gdb.modula2
Date: Mon, 25 Jun 2012 20:28:00 -0000	[thread overview]
Message-ID: <87mx3rb0h6.fsf@fleche.redhat.com> (raw)

I'm checking this in.

This changes gdb.modula2 to use standard_testfile and prepare_for_testing.

Regtested on x86-64 Fedora 16.

Tom

2012-06-25  Tom Tromey  <tromey@redhat.com>

	* gdb.modula2/unbounded-array.exp: Use standard_testfile,
	prepare_for_testing.

Index: gdb.modula2/unbounded-array.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.modula2/unbounded-array.exp,v
retrieving revision 1.8
diff -u -r1.8 unbounded-array.exp
--- gdb.modula2/unbounded-array.exp	16 Jan 2012 16:21:51 -0000	1.8
+++ gdb.modula2/unbounded-array.exp	25 Jun 2012 20:27:14 -0000
@@ -17,20 +17,13 @@
 # the elements of an unbounded array using the Modula-2 language mode of
 # gdb.
 
-set testfile "unbounded1"
-set srcfile ${testfile}.c
-set binfile ${objdir}/${subdir}/${testfile}
+standard_testfile unbounded1.c
 
-if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug quiet}] != "" } {
-    untested "Couldn't compile ${srcfile}"
+if {[prepare_for_testing $testfile.exp $testfile $srcfile {debug quiet}]} {
+    untested $testfile.exp
     return -1
 }
 
-gdb_exit
-gdb_start
-gdb_reinitialize_dir $srcdir/$subdir
-gdb_load ${binfile}
-
 if ![runto foo] then {
     perror "couldn't run to breakpoint foo"
     continue


             reply	other threads:[~2012-06-25 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 20:28 Tom Tromey [this message]
2012-06-26  9:37 ` Gaius Mulley

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=87mx3rb0h6.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@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