This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch] add gdb.threads/pthread_cond_wait.* in fnchange.lst
- From: Eli Zaretskii <eliz at gnu dot org>
- To: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- Cc: brobecker at gnat dot com, gdb-patches at sources dot redhat dot com
- Date: 20 May 2004 08:41:46 +0200
- Subject: Re: [patch] add gdb.threads/pthread_cond_wait.* in fnchange.lst
- References: <20040520025754.1761C4B104@berman.michael-chastain.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 19 May 2004 22:57:54 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> My understanding is that the test suite does not actually *run*
> on djgpp. So the files just need to un-tar cleanly, which means
> only one '.' in the filename and no '+' and the default truncation
> to 8.3 has to give unique names. So your files would have unpacked
> to testsuit/gdb.thr/pthread_.exp and testsuit/gdb.thr/pthread_.c
> and that would be okay (just barely, because of pthreads.exp).
>
> Eli is the expert on this ... Eli?
You are absolutely right.
Note that, while the test suite cannot be run with the DJGPP build
(because `expect' needs async subprocesses that DJGPP doesn't
support), even if it could be run, the truncated names would work.
That is because, when a program tries to open a file whose name is
pthread_cond_wait.exp, the OS silently truncates that to the 8+3
limits, yielding pthread_.exp and looks for a file by that truncated
name. That's why we can compile GDB itself (which involves the
compiler, Make, the linker, etc. having to open the source files),
although many of its source files have names in excess of 8+3 limits.