From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] gdbadmin/ss/gdb_find.sh cleanup
Date: Wed, 22 Apr 2009 21:41:00 -0000 [thread overview]
Message-ID: <001601c9c393$04ef72e0$0ece58a0$@u-strasbg.fr> (raw)
In-Reply-To: <20090422175643.GA22514@adacore.com>
Hi Joel,
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Wednesday, April 22, 2009 7:57 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFA] gdbadmin/ss/gdb_find.sh cleanup
>
> > -name signals -prune -o \
>
> I can't find a "signals" directory. Can you double-check and remove
> this line if I'm right? (if it makes sense to you too)
Everything from signals directory seems to have been moved to
common directory by Doug Evans see ChangeLog entry from 2009-03-01.
I never use -P option for 'cvs up'
and thus have a lot of empty directories lying around!
> > -name testsuite -prune -o \
> > -name gdbserver -prune -o \
>
> I wonder if we want to start tracking the gdbserver sources as well.
> Just a thought...
>
> > -name gnulib -prune -o \
> > -name rdi-share -prune -o \
>
> Can't find this directory either...
>
> > -name remote-mips.c -prune -o \
>
> This file started being excluded in Jan 2005. There's definitely
> been some activity on the associated target, so I'm thinking it might
> make sense to stop excluding it.
>
> > 'sh64*' and 'remote-mips.c'
> > sh64* covers
> > gdb/sh64-tdep.c file
> > and
> > config/sh64 directory.
> Strange, I can't find that config/sh64 directory either.
>
Strange because there is a sh64 in gdb/config/CVS/entries
but on the other hand, when I do 'cvs up'
sh64 directory is not listed...
> > Why are those patterns excluded?
>
> Here what the CVS log says about the change that introduced the
> exclusion:
>
> revision 1.7
> date: 2004/08/03 13:09:19; author: cagney; state: Exp; lines: +9
> -2
> Ignore (hardwired) broken targets.
>
> Since then, it appears that Corinna Vinshen has done some work to
> revive the target. So we might again want to remove them from the
> exclusion list. To be checked with Corinna?
>
> > < -name ada-lex.c -prune -o \
>
> DanielJ specifically removed this file from the list. I'm not sure
> whether anything changed that would make us change our decision.
> This is a generated file - perhaps we should check the source .l
> file instead (which I think we do).
>
> > < -name cp-name-parser.c -prune -o \
>
> Same here. This is a generated file.
>
> > < -name stop-gdb.c -prune -o \
> > 19,21d15
> > < -name lynx-nat.c -prune -o \
> > < -name ppc-bdm.c -prune -o \
> > < -name ppc-bdm.c -prune -o \
> > 23,24d16
> > < -name remote-sds.c -prune -o \
> > < -name remote-sds.c -prune -o \
>
> The rest seems OK to me.
>
> --
> Joel
Below is the new version of gdb_find.sh
that I checked in:
(the diff file is just as big, so I send the new version directly)
Thanks, Joel,
Pierre
$ cat gdb_find.sh
#!/bin/sh
# A find that prunes files that GDB users shouldn't be interested in.
find "$@" \
-name testsuite -prune -o \
-name gdbserver -prune -o \
-name gnulib -prune -o \
-name osf-share -prune -o \
-name '*-stub.c' -prune -o \
-name '*-exp.c' -prune -o \
-name ada-lex.c -prune -o \
-name cp-name-parser.c -prune -o \
-name remote-mips.c -prune -o \
-type f -name '*.[lyhc]' -print
prev parent reply other threads:[~2009-04-22 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:42 Pierre Muller
2009-04-22 17:57 ` Joel Brobecker
2009-04-22 21:41 ` Pierre Muller [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='001601c9c393$04ef72e0$0ece58a0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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