Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PP?] [PATCH] testsuite: Cleanup some temp dirs with gdb-index files
Date: Fri, 14 May 2021 09:26:17 -0400	[thread overview]
Message-ID: <41e8702a-b0cb-57dd-efa2-4e059ec7c9d1@polymtl.ca> (raw)
In-Reply-To: <AM8PR10MB4708C1B2AA338675E5E9B2F1E4509@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>

On 2021-05-14 9:20 a.m., Bernd Edlinger wrote:
> Hi,
> 
> I'd like to cleanup some files/directories which
> remain after the gdb testsute runs.
> 
> I want to avoid using "rm -rf ..." since that can be dangerous.
> Therefore I remove the *.gdb-index files, if any, and use
> rmdir instead.  I am not sure if there is a better way,
> instead of using "remote_exec host sh -c" to do the globbing.
> 
> Tested on x86_64-pc-linux-gnu.
> Is it OK for trunk?
> 
> 
> gdb/testsuite:
> 2021-05-14  Bernd Edlinger  <bernd.edlinger@hotmail.de>
> 
>         * gdb.base/index-cache.exp: Cleanup $cache_dir/*.gdb-index and
>         remove the directory.
>         * gdb.dwarf2/per-bfd-sharing.exp: Likewise.
> 

LGTM, but I have one question: if the rm or rmdir ever fails (because
there are additional files to delete, for example), would we know about
it or would it silently fail?  I think it would be nice if the error
was noisy so we could fix it.

Simon

  reply	other threads:[~2021-05-14 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 13:20 Bernd Edlinger
2021-05-14 13:26 ` Simon Marchi via Gdb-patches [this message]
2021-05-14 15:03   ` [PP?] " Bernd Edlinger
2021-05-14 15:23     ` Simon Marchi via Gdb-patches
2021-05-14 15:39       ` Bernd Edlinger
2021-05-14 15:45         ` Simon Marchi via Gdb-patches

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=41e8702a-b0cb-57dd-efa2-4e059ec7c9d1@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=bernd.edlinger@hotmail.de \
    --cc=simon.marchi@polymtl.ca \
    /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