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: Thu, 5 Jun 2003 19:18:26 +0200 (CEST)
From: Pavel Tsekov <ptsekov AT gmx DOT net>
X-X-Sender: ptsekov AT moria DOT atlanticsky DOT com
To: cygwin AT cygwin DOT com
Subject: RE: mc segfaults
In-Reply-To: <Pine.GSO.4.44.0306051247070.25752-100000@slinky.cs.nyu.edu>
Message-ID: <Pine.LNX.4.44.0306051916560.6329-100000@moria.atlanticsky.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Jun 2003, Igor Pechtchanski wrote:

> This may be a Cygwin-specific problem.  On Cygwin, /etc/passwd doesn't
> play as key a role as it does on other Unix systems (e.g., it's not
> required for logging in on the console).  Thus, it's quite possible that
> someone will attempt to run other applications when missing /etc/passwd
> entries, and what is an abnormal situation on Unix systems might be simply
> an annoying omission in Cygwin.  I don't think the assert/crash is
> justified in this case.  At the very least it should have a more
> informative error message, and a better solution would be to simply remove
> the assert and conditionalize the following code on (pwd != NULL)
> (possibly with #ifdef __CYGWIN__ around it, although I don't think it'll
> affect the other Unix systems all that much).  I'm not all that familiar
> with mc, so the usual disclaimers apply to the above.

Ok, I'll see what I can do.


--
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/