Re: [PATCH] [gdb/testsuite] Fix gdb.base/local-env.exp on remote host

Tom Tromey
2025-12-18T18:59:29Z

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> This doesn't work with remote host, so declare the test unsupported. Likewise
Tom> in gdb.base/environ.exp.

Tom> -gdb_assert {$saw_env == 1} "show environment displayed variable"
Tom> +set test "show environment displayed variable"
Tom> +if {[is_remote host]} {
Tom> + unsupported $test
Tom> +} else {
Tom> + gdb_assert {$saw_env == 1} $test

I've been under the impression we usually use unsupported to indicate
that an entire .exp is being skipped, and for individual tests we simply
don't invoke them.

However I guess I don't really know. Do we have other cases like this?

Tom