[PATCH] [gdb/testsuite] Fix can_spawn_for_attach_1 consistency check

Alexandra Petlanova Hajkova ahajkova@redhat.com
Mon May 20 13:47:29 GMT 2024


>
>  gdb_caching_proc can_spawn_for_attach_1 {} {
> +    # For the benefit of gdb-caching-proc-consistency.exp, which
> +    # calls can_spawn_for_attach_1 directly.  Keep in sync with
> +    # can_spawn_for_attach.
> +    if { [is_remote target] || [target_info exists use_gdb_stub] } {
> +       return 0
> +    }
> +
>      # Assume yes.
>      set res 1
>
>
> This solution looks reasonable to me. Also I've tried running this test on
aarch64 but it always passes there:

 make check RUNTESTFLAGS="--target_board=native-gdbserver"
TESTS=gdb.testsuite/gdb-caching-proc-consistency.exp

 Reviewed-By: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/gdb-patches/attachments/20240520/8b7db733/attachment.htm>


More information about the Gdb-patches mailing list