Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>, Doug Evans <dje@google.com>,
	Joel Brobecker	<brobecker@adacore.com>
Subject: Re: Ping: [PATCH] testsuite: Add (extensive) hardware breakpoint testing
Date: Tue, 28 Feb 2012 19:49:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1202281934340.4811@tp.orcam.me.uk> (raw)
In-Reply-To: <4F4D0B18.5040402@redhat.com>

On Tue, 28 Feb 2012, Pedro Alves wrote:

> I read the thread from the start, and I diffed the new proposed test against break.exp,
> and I think we should go ahead and put this in.  Only a couple remarks below.
> 
> > +#   Copyright 2012 Free Software Foundation, Inc.
> 
> I think dropping the original copyright years was a mistake.

 TBH I've never been particularly convinced to do that since this is 
derived work (and clearly not in a trivial amount).  Thanks for backing me 
up.

> > +if { [prepare_for_testing hbreak2.exp "break" {break.c break1.c} {debug nowarnings}] } {
> 
> s/"break"/"hbreak2", so that running this test doesn't overwrite break.exp's binary.
> More instances of this.

 Good point, apparently there is just one other place requiring this 
adjustment.

 Thanks for your review, here's the resulting update.  Any further 
thoughts, anyone?

  Maciej

Index: gdb-fsf-trunk-quilt/gdb/testsuite/gdb.base/hbreak2.exp
===================================================================
--- gdb-fsf-trunk-quilt.orig/gdb/testsuite/gdb.base/hbreak2.exp	2012-02-28 18:50:20.455581421 +0000
+++ gdb-fsf-trunk-quilt/gdb/testsuite/gdb.base/hbreak2.exp	2012-02-28 18:49:31.835596342 +0000
@@ -1,4 +1,5 @@
-#   Copyright 2012 Free Software Foundation, Inc.
+#   Copyright 1988, 1990-1992, 1994-2000, 2002-2003, 2007-2012 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
@@ -19,7 +20,7 @@
 # the number available.
 
 
-if { [prepare_for_testing hbreak2.exp "break" {break.c break1.c} {debug nowarnings}] } {
+if { [prepare_for_testing hbreak2.exp "hbreak2" {break.c break1.c} {debug nowarnings}] } {
     return -1
 }
 set srcfile break.c
@@ -530,7 +531,7 @@ test_next_with_recursion
 # Build a new file with optimization enabled so that we can try breakpoints
 # on targets with optimized prologues.
 
-if { [prepare_for_testing hbreak2.exp "breako2" {break.c break1.c} {debug nowarnings optimize=-O2}] } {
+if { [prepare_for_testing hbreak2.exp "hbreak2o2" {break.c break1.c} {debug nowarnings optimize=-O2}] } {
     return -1
 }
 


  reply	other threads:[~2012-02-28 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 12:13 Maciej W. Rozycki
2011-11-11 17:08 ` Doug Evans
2011-11-11 17:43   ` Joel Brobecker
2011-11-11 18:59     ` Maciej W. Rozycki
2011-11-12  0:08       ` Pedro Alves
2011-11-14 13:18         ` Maciej W. Rozycki
2011-11-11 20:12   ` Maciej W. Rozycki
2011-12-08 15:33     ` Maciej W. Rozycki
2012-02-27 21:30       ` Ping: " Maciej W. Rozycki
2012-02-28 17:27         ` Pedro Alves
2012-02-28 19:49           ` Maciej W. Rozycki [this message]
2012-03-01 11:42             ` Pedro Alves
2012-03-01 21:02               ` Maciej W. Rozycki

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=alpine.DEB.1.10.1202281934340.4811@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=dje@google.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