-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul,
Timing problems are very tricky. Could you try to collect just a bit
more inforamtion?
On the cvs command, use a -ttt switch to get tracing information
(i.e., 'cvs -ttt -z3 ...') you might also try in a separate run
setting the CVS_CLIENT_LOG environment variable.
CVS_CLIENT_LOG=cvs-client-log; export CVS_CLIENT_LOG
This will put into the cvs-client-log.in and cvs-client-log.out files.
It is possible that adding this debugging information will also not let
the problem exhibit itself.
Thank you!
-- Mark
Paul Eggert <[EMAIL PROTECTED]> writes:
> Here's how I can easily reproduce the bug:
>
> $ rm -fr gnulib
> $ cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/gnulib co gnulib
> cvs checkout: Updating gnulib
> U gnulib/COPYING
> U gnulib/ChangeLog
> ...
> U gnulib/tests/test-stpncpy.c
> U gnulib/tests/test-stpncpy.out.aix433
> U gnulib/tests/test-stpncpy.out.glibc
>
> At this point CVS hangs.
>
> I've reproduced the problem both in Debian GNU/Linux 3.1 x86, and on
> Solaris 8 (sparc, 64-bit).
>
> The problem does not occur with CVS 1.12.9 (as packaged by Debian
> stable).
>
> If I run CVS under "strace" on Debian, it works, so possibly it's a
> timing-relating issue.
>
>
> _______________________________________________
> Bug-cvs mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/bug-cvs
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)
iD8DBQFFC7jmCg7APGsDnFERAlrmAKDvlHJtF3MiW4j1DURAjmBAqRZnpwCdE2AK
mFWPAXW4nW50bS/EdlBsqaM=
=b+3D
-----END PGP SIGNATURE-----
_______________________________________________
Bug-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/bug-cvs
