Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Use clean_restart where possible
Date: Wed, 11 Nov 2020 10:49:07 -0500	[thread overview]
Message-ID: <d3032604-172b-2491-26c0-a6bcfcda30bd@simark.ca> (raw)
In-Reply-To: <1fe630a0-0d44-8e04-b905-09a727ba7c56@suse.de>

On 2020-11-11 4:18 a.m., Tom de Vries wrote:
> [ was: Re: [PATCH][gdb/testsuite] Add
> gdb.dwarf2/fission-multi-cu-clang.exp ]
> On 11/10/20 8:21 PM, Simon Marchi wrote:
>>> +gdb_exit
>>> +gdb_start
>>> +gdb_reinitialize_dir $srcdir/$subdir
>>
>> clean_restart?
>
> Hmm yes, that's one of those things I just pick up by starting a
> test-case using a copy of another test-case.
>
> So, let's fix this in those other test-cases as well.
>
> FWIW, I'm open to suggestions to do this in an easier way than using awk.
>
> Thanks,
> - Tom
>

I don't know awk, so that looks very impressive to me!  I think it's a
good idea to fix them once and for all.

It would be worth grepping for gdb_reinitialize_dir, to catch more spots
that can be changed.  For example, in gdb.base/overlays.exp we have the
sequence without gdb_exit:

 49 gdb_start
 50 gdb_reinitialize_dir $srcdir/$subdir
 51 gdb_load ${binfile}

Those can also be changed with clean_restart.

Simon

      reply	other threads:[~2020-11-11 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 16:40 [PATCH][gdb/testsuite] Add gdb.dwarf2/fission-multi-cu-clang.exp Tom de Vries
2020-11-10 19:21 ` Simon Marchi
2020-11-11  9:18   ` [PATCH][gdb/testsuite] Use clean_restart where possible Tom de Vries
2020-11-11 15:49     ` Simon Marchi [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=d3032604-172b-2491-26c0-a6bcfcda30bd@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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