From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Remove Java support
Date: Thu, 06 Oct 2016 16:40:00 -0000 [thread overview]
Message-ID: <87eg3te9wn.fsf@tromey.com> (raw)
In-Reply-To: <87int5ebke.fsf@tromey.com> (Tom Tromey's message of "Thu, 06 Oct 2016 09:34:09 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> Thanks for digging that up. I've restored this test and I'll re-regtest
Tom> and repost the patch before pushing.
Rather than re-send the entire large patch, I'm just appending the new
setshow.exp part.
Tom
diff --git a/gdb/testsuite/gdb.base/setshow.exp b/gdb/testsuite/gdb.base/setshow.exp
index 2a86cdd..93dd926 100644
--- a/gdb/testsuite/gdb.base/setshow.exp
+++ b/gdb/testsuite/gdb.base/setshow.exp
@@ -211,10 +211,10 @@ gdb_test "show history size" "The size of the command history is 100..*" "show h
gdb_test "set language asm" ".*" "set language asm"
#test show language asm
gdb_test "show language" "The current source language is \"asm\"..*" "show language (asm)"
-#test set language java, with a trailing space
-gdb_test_no_output "set language java " "set language java"
-#test show language java
-gdb_test "show language" "The current source language is \"java\"..*" "show language (java)"
+#test set language rust, with a trailing space
+gdb_test_no_output "set language rust " "set language rust"
+#test show language rust
+gdb_test "show language" "The current source language is \"rust\"..*" "show language (rust)"
#test completion for set language.
gdb_test "complete set language min" "set language minimal" \
"complete set language minimal"
next prev parent reply other threads:[~2016-10-06 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:52 Tom Tromey
2016-10-05 16:04 ` Eli Zaretskii
2016-10-06 13:32 ` Pedro Alves
2016-10-06 15:34 ` Tom Tromey
2016-10-06 16:14 ` Pedro Alves
2016-10-06 16:19 ` Tom Tromey
2016-10-06 16:40 ` Tom Tromey [this message]
2016-10-06 16:45 ` 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=87eg3te9wn.fsf@tromey.com \
--to=tom@tromey.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