Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Automatically handle includes in testsuite/lib/
Date: Sat, 16 Aug 2025 10:59:05 -0700	[thread overview]
Message-ID: <20250816105721.5f0d5da8@f41-zbm-amd> (raw)
In-Reply-To: <20250813004100.2525141-1-pedro@palves.net>

On Wed, 13 Aug 2025 01:41:00 +0100
Pedro Alves <pedro@palves.net> wrote:

> Instead of manually calling lappend_include_file in every testcase
> that needs to include a file in testsuite/lib/, handle testsuite/lib/
> includes automatically in gdb_compile.
> 
> As an example, gdb.base/backtrace.exp is adjusted to no longer
> explicitly call lappend_include_file for testsuite/lib/attributes.h.
> 
> Tested on x86-64 GNU/Linux with both:
> 
>  $ make check RUNTESTFLAGS=" \
>      --host_board=local-remote-host-native \
>      --target_board=local-remote-host-native \
>      HOST_DIR=/tmp/foo/" \
>      TESTS="gdb.base/backtrace.exp"
> 
> and:
> 
>  $ make check TESTS="gdb.base/backtrace.exp"
> 
> and confirming that the testcase still compiles and passes cleanly.
> 
> Also ran full testsuite on x86-64 GNU/Linux in normal mode.
> 
> Change-Id: I5ca77426ea4a753a995c3ad125618c02cd952576
> ---
>  gdb/testsuite/gdb.base/backtrace.exp |  6 +--
>  gdb/testsuite/lib/gdb.exp            | 63 ++++++++++++++++++++++++++++
>  2 files changed, 64 insertions(+), 5 deletions(-)

LGTM.

Approved-by: Kevin Buettner <kevinb@redhat.com>


  reply	other threads:[~2025-08-16 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  0:41 Pedro Alves
2025-08-16 17:59 ` Kevin Buettner [this message]
2025-08-22 18:29   ` 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=20250816105721.5f0d5da8@f41-zbm-amd \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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