public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] gdb/testsuite: handle errors better in test_compiler_info
@ 2022-06-09 13:41 Andrew Burgess
  0 siblings, 0 replies; only message in thread
From: Andrew Burgess @ 2022-06-09 13:41 UTC (permalink / raw)
  To: gdb-cvs

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0e471fde0742bbbc8e34f0d082d1b35c19aee96f

commit 0e471fde0742bbbc8e34f0d082d1b35c19aee96f
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Wed Jun 8 14:04:36 2022 +0100

    gdb/testsuite: handle errors better in test_compiler_info
    
    Now that get_compiler_info might actually fail (if the language is not
    handled), then we should try to handle this failure better in
    test_compiler_info.
    
    After this commit, if get_compiler_info fails then we will return a
    suitable result depending on how the user called test_compiler_info.
    
    If the user does something like:
    
      set version [test_compiler_info "" "unknown-language"]
    
    Then test_compiler_info will return an empty string.  My assumption is
    that the user will be trying to match 'version' against something, and
    the empty string hopefully will not match.
    
    If the user does something like:
    
      if { [test_compiler_info "some_pattern" "unknown-language"] } {
        ....
      }
    
    Then test_compiler_info will return false which seems the obvious
    choice.
    
    There should be no change in the test results after this commit.

Diff:
---
 gdb/testsuite/lib/gdb.exp | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index e530ba05a61..e28c33e8455 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -4199,7 +4199,17 @@ proc get_compiler_info {{language "c"}} {
 
 proc test_compiler_info { {compiler ""} {language "c"} } {
     global compiler_info
-    get_compiler_info $language
+
+    if [get_compiler_info $language] {
+	# An error will already have been printed in this case.  Just
+	# return a suitable result depending on how the user called
+	# this function.
+	if [string match "" $compiler] {
+	    return ""
+	} else {
+	    return false
+	}
+    }
 
     # If no arg, return the compiler_info string.
     if [string match "" $compiler] {


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-06-09 13:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-09 13:41 [binutils-gdb] gdb/testsuite: handle errors better in test_compiler_info Andrew Burgess

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).