delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/06/14/18:21:14

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
Message-Id: <5.1.0.14.0.20020614181407.01f9af38@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Fri, 14 Jun 2002 18:17:24 -0400
To: Len Giambrone <frodo AT MIT DOT EDU>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: 1.3.10: ttyslot dying, Windows 2000 Server
Cc: cygwin AT cygwin DOT com
In-Reply-To: <tmlr8j9wlzj.fsf@small-gods.mit.edu>
References: <"Larry Hall's message of "Fri, 14 Jun 2002 17:50:26 -0400">
<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020614173908 DOT 05ffd8c8 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0

At 06:09 PM 6/14/2002, Len Giambrone wrote:
>> >When I use drwtsn32 to look at what caused the crash, it tells me that
>> >"ttyslot" is the culprit.  By looking at logs, it's clear that ttyslot is
>> >dying in a variety of standard unix programs, like md5sum, tar, etc.
>> 
>> 
>> What's ttyslot?  Answering this and understanding more about it might help
>> you solve your problem.  It's clear this isn't a Cygwin problem per-se 
>> because a search of http://cygwin.com/packages/ for ttyslot turns up nothing.
>> I'll leave it as an exercise for the reader to understand why this indicates
>> it's not a Cygwin issue. ;-)
>
>Perhaps I should have said "ttyslot()".
>
>It's a function in the cygwin.dll.  From cygwin-1.3.10-1/winsup/cygwin/tty.cc:
>
>extern "C"
>int
>ttyslot (void)
>{
>  if (NOTSTATE (myself, PID_USETTY))
>    return -1;
>  return myself->ctty;
>}


OK, if you're saying that Dr. Watson is pointing to ttyslot() in the Cygwin
DLL with it's stack trace, then that would be a Cygwin issue.  ;-)  Sorry,
I don't have any further suggestions for this particular issue at this 
time.  But thanks for the clarification.

I'd still recommend cleaning up your environment.  You want to be sure you're
using Cygwin tools when they're necessary (rather than other name-alikes).




Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019