Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Guinevere Larsen <guinevere@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb, testsuite: fix gdb.base/save-history.exp for native-extended-gdbserver
Date: Fri, 17 Apr 2026 13:33:34 +0000	[thread overview]
Message-ID: <DM4PR11MB7303A5847C0F6C33D1BDA3CCC4202@DM4PR11MB7303.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f407d4dd-0f60-4baf-aa2a-02e9e9893a29@redhat.com>

On Friday, April 17, 2026 2:54 PM, Guinevere Larsen wrote:
> On 4/17/26 7:35 AM, Tankut Baris Aktemur wrote:
> > When executed with the native-extended-gdbserver board file, we get
> >
> >    FAIL: gdb.base/save-history.exp: check history contents
> >
> > This is because the history file contains an extra line for the
> > command 'target extended-remote ...'.  To keep the test
> > straightforward, skip it if using the extended-remote target.
> > ---
> >   gdb/testsuite/gdb.base/save-history.exp | 7 +++++++
> >   1 file changed, 7 insertions(+)
> >
> > diff --git a/gdb/testsuite/gdb.base/save-history.exp
> b/gdb/testsuite/gdb.base/save-history.exp
> > index bb7a56b2a72..5ca47f3bc1f 100644
> > --- a/gdb/testsuite/gdb.base/save-history.exp
> > +++ b/gdb/testsuite/gdb.base/save-history.exp
> > @@ -19,6 +19,13 @@
> >
> >   require {!is_remote host}
> >
> > +# A remote server adds extra setup commands in history.  To keep the
> > +# test straighforward, skip extended-remote target.
> > +if {[target_info gdb_protocol] == "extended-remote"} {
> > +    unsupported "test not aimed for extended-remote target"
> > +    return
> > +}
> > +
> >   gdb_start
> >
> >   # Get something in history.
> 
> I feel like the test would be equally straight forward to make the
> following change instead (comment omitted because I was lazy in local
> testing):
> 
> --- a/gdb/testsuite/gdb.base/save-history.exp
> +++ b/gdb/testsuite/gdb.base/save-history.exp
> @@ -30,6 +30,9 @@ gdb_test_no_output "save history $filename" \
> 
>   set expected "set height 0\n"
>   append expected "set width 0\n"
> +if {[target_info gdb_protocol] == "extended-remote"} {
> +    append expected "target extended-remote localhost:2345\n"

We cannot hardcode the port number but it should be possible to use
$gdbserver_gdbport.  I'll run a parallel make-check to test.

-Baris

> +}
>   append expected "print 23\n"
>   append expected "save history $filename\n"
> 
> --
> Cheers,
> Guinevere Larsen
> It/she


Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

      reply	other threads:[~2026-04-17 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 10:35 Tankut Baris Aktemur
2026-04-17 12:54 ` Guinevere Larsen
2026-04-17 13:33   ` Aktemur, Tankut Baris [this message]

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=DM4PR11MB7303A5847C0F6C33D1BDA3CCC4202@DM4PR11MB7303.namprd11.prod.outlook.com \
    --to=tankut.baris.aktemur@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    /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