From 7ec0e36e9f102279fa2aa2138fb2bd09fdf4cd49 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Tue, 28 Mar 2023 10:22:48 +0200 Subject: [PATCH] [gdb/testsuite] Unsupport gdb.rust for remote host With test-case gdb.rust/watch.exp and remote host I run into: ... Executing on host: gcc watch.rs -g -lm -o watch (timeout = 300) ... ld:watch.rs: file format not recognized; treating as linker script ld:watch.rs:1: syntax error ... UNTESTED: gdb.rust/watch.exp: failed to prepare ... The problem is that find_rustc returns "" for remote host, so we fall back to gcc, which fails. Fix this by returning 0 in allow_rust_tests for remote host. Tested on x86_64-linux. --- gdb/testsuite/lib/gdb.exp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 14ce39e8ed7..0d064017f09 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -2479,6 +2479,11 @@ proc allow_rust_tests {} { return 0 } + if { [is_remote host] } { + # Proc find_rustc returns "" for remote host. + return 0 + } + # The rust compiler does not support "-m32", skip. global board board_info set board [target_info name] -- 2.30.2