public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>,
	gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH, testsuite] Update gdb startup text in selftest.exp
Date: Wed, 13 Jun 2018 11:50:00 -0000	[thread overview]
Message-ID: <79521339-876f-f14a-c427-79f2e79f994a@redhat.com> (raw)
In-Reply-To: <20180612140945.drjp7rent7mkeoam@localhost.localdomain>

[Tromey's current address fixed]

Hi Tom,

On 06/12/2018 03:10 PM, Tom de Vries wrote:
> Hi,
> 
> atm selftest.exp fails for me.
> 
> One of the reasons is that in c61b06a19a34baab66e3809c7b41b0c31009ed9f (Remove
> some text from --version output) an eol was added after "There is NO
> WARRANTY, to the extent permitted by law".
> 
> This patch updates the matching of the gdb startup message in selftest.exp
> accordingly.
> 
> Tested selftest.exp (with two other selftest.exp related fixes applied).
> 
> OK for trunk?
> 
> Thanks,
> - Tom
> 
> [gdb/testsuite] Update gdb startup text in selftest.exp

You were probably already going to do it, but just in case,
since it's not practice in gcc, please include the rationale above
in the commit log (without the "Hi", "OK for trunk", etc.
bits of course.)  See "git log gdb/" for examples.

OK with that change.

That test could be made a lot more readable with use of multi_line.

Thanks,
Pedro Alves

> 
> 2018-06-12  Tom de Vries  <tdevries@suse.de>
> 
> 	* gdb.gdb/selftest.exp (test_with_self): Update gdb startup text.
> 
> ---
>  gdb/testsuite/gdb.gdb/selftest.exp | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/testsuite/gdb.gdb/selftest.exp b/gdb/testsuite/gdb.gdb/selftest.exp
> index 20f34983ef..314bddb8bf 100644
> --- a/gdb/testsuite/gdb.gdb/selftest.exp
> +++ b/gdb/testsuite/gdb.gdb/selftest.exp
> @@ -66,7 +66,7 @@ proc test_with_self { } {
>  	set test "xgdb is at prompt"
>  	gdb_test_multiple "continue" $test {
>  	    -i "$inferior_spawn_id"
> -	    -re "GNU gdb \[0-9\.\]*.*Copyright \\(C\\) \[0-9\]* Free Software Foundation, Inc.*License GPLv3\\+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.*This is free software: you are free to change and redistribute it.*There is NO WARRANTY, to the extent permitted by law.  Type \"show copying\".*and \"show warranty\" for details.*This GDB was configured as .*$gdb_prompt $" {
> +	    -re "GNU gdb \[0-9\.\]*.*Copyright \\(C\\) \[0-9\]* Free Software Foundation, Inc.*License GPLv3\\+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.*This is free software: you are free to change and redistribute it.*There is NO WARRANTY, to the extent permitted by law\..*Type \"show copying\".*and \"show warranty\" for details.*This GDB was configured as .*$gdb_prompt $" {
>  		pass $test
>  	    }
>  	}
> 

  reply	other threads:[~2018-06-13 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:10 Tom de Vries
2018-06-13 11:50 ` Pedro Alves [this message]
2018-06-14 11:51   ` [pushed] gdb.gdb/selftest.exp, Use multi_line to build gdb's expected startup output (Re: [PATCH, testsuite] Update gdb startup text in selftest.exp) Pedro Alves

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=79521339-876f-f14a-c427-79f2e79f994a@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).