RE: Windows CVS 1.12.12.1 Latest + Patch - "version" Command Hangs

[Conrad T. Pino]

> From: Derek Price [mailto:derek@ximbiot.com]
> 
> >What does "buffer" mean in this context?
> 
> All CVS client/server communication is done through a series of
> "buffers", defined with an abstract API in buffer.[ch].  Individual
> buffer types need to be declared with the fd_buffer_initialize,
> socket_buffer_initialize, compress_buffer_initialize, etc. functions,
> but they may then be chained and accessed through only the topmost
> buffer in the chain via the generic API set up in buffer.[ch].

Which is the correction function to call for :ext: initialization?

> The code that selects on the fd in fd_buffer_input is about a year old
> now, and was contained in at least 1.12.12, so I'm unsure why this
> problem just started cropping up now.

CVS version 1.12.12 has the same problem with :ext: via SSH.

H:\cvs-1.12.12>windebug\cvs -v

Concurrent Versions System (CVS) 1.12.12 (client)

Copyright (C) 2005 Free Software Foundation, Inc.

Senior active maintainers include Larry Jones, Derek R. Price,
and Mark D. Baushke.  Please see the AUTHORS and README files from the CVS
distribution kit for a complete list of contributors and copyrights.

CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.

Specify the --help option for further information about CVS

H:\cvs-1.12.12>windebug\cvs version
Client: Concurrent Versions System (CVS) 1.12.12 (client)
Server: cvs [version aborted]: reading from server: No such file or directory

H:\cvs-1.12.12>Unable to write to standard output

> Is it possible that something
> changed in the code that starts up the windows :ext: server such that
> the piped_child function started returning an fd rather than a socket?

I don't know how to begin answering this question.
Does version 1.12.12 being broken also help here?