Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 7 May 2004 18:53:27 -0500
From: Brian Ford <ford AT vss DOT fsi DOT com>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: cvs HEAD: rlogin broken
In-Reply-To: <Pine.CYG.4.58.0405071750540.2520@fordpc.vss.fsi.com>
Message-ID: <Pine.CYG.4.58.0405071848380.2520@fordpc.vss.fsi.com>
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0405071619410 DOT 2684 AT fordpc DOT vss DOT fsi DOT com> <20040507213238 DOT GA16162 AT cygbert DOT vinschen DOT de> <Pine DOT CYG DOT 4 DOT 58 DOT 0405071750540 DOT 2520 AT fordpc DOT vss DOT fsi DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes

On Fri, 7 May 2004, Brian Ford wrote:

> On Fri, 7 May 2004, Corinna Vinschen wrote:
>
> > On May  7 16:28, Brian Ford wrote:
> > > Just a heads up.  Current cvs HEAD cygwin1.dll has broken rlogin.
> [snip]
> > > I'll look if I have time later, but I thought Corinna might want to know.
> >
> > WFM(tm)
>
> Darn, I was hoping it would be as easy to reproduce for you as it is for
> me.  Ah..., the joys of a hyperthreaded machine, I bet.  I'll see what I
> can dig up.  Thanks for the reply.

I'm about to give up and go home for the weekend.  Here is where rlogin is
stuck in the child process:

#16 0x61049408 in fhandler_socket::wait (this=0x616e50a4, event=0x6e8)
    at ../../../../cygwin/winsup/cygwin/fhandler_socket.cc:723
#17 0x61049b92 in fhandler_socket::recvmsg (this=0x616e50a4, msg=0x22eb10,
    flags=0, tot=8192) at ../../../../cygwin/winsup/cygwin/fhandler.h:365
#18 0x6104963f in fhandler_socket::readv (this=0x616e50a4, iov=0x22ebc0,
---Type <return> to continue, or q <return> to quit---
    iovcnt=1, tot=8192)
    at ../../../../cygwin/winsup/cygwin/fhandler_socket.cc:800
#19 0x6109fc2e in readv (fd=3, iov=0x22ebc0, iovcnt=1)
    at ../../../../cygwin/winsup/cygwin/cygheap.h:303
#20 0x6109f95c in read (fd=3, ptr=0x404070, len=8192)
    at ../../../../cygwin/winsup/cygwin/syscalls.cc:369

just one stupid question...  I'm probably way off base, but it looks like
the WSAEnumNetworkEvents call on line 726 of fhandler_socket.cc might
return events for the parent process's copy of the socket as well as the
child's in a forked process.  Could that be an issue?

I'm just grasping at straws that I don't understand and trying to be
helpful at the same time :-).

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/