X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=lhHTwSBSTZs9jZWnuecYGcDBBXZFuR1x4laiPwGtvbHaFdNs6h5JB I+zzRp0rBt+PC6Fq+e/bW6tKPp+iw5CKU+I5+Q5wEYPgGyj7g0mb6qgfzM1BQkqV aQ6LWWcDE6gcLBOMQ2wUHHlmXG6/YsxlAj8Ydpyu/3NESajSREJv/U= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=7ouCd/L5J9ZCeUieQWznUk7QMnQ=; b=lyFGmDEqHDbINRMdVCYHvJalpVto pvYvCcVL5YjOfz0nf0WyVsW6I2jKNOKHezjtDgs+EiqQWPEeBIfYv7G3Il7DvIay AI9tjF3z6C62db+evTMO80d9sK6jOJEwgDN0+hPSJ0Ce0nYXs3C0KMJky2tiVmXb e1Gyox0e5G2U+9U= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Fri, 21 Jun 2013 10:21:55 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Failed assertion in path.cc (path_conv::check) Message-ID: <20130621082155.GG1620@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51C40016 DOT 3000409 AT cwilson DOT fastmail DOT fm> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51C40016.3000409@cwilson.fastmail.fm> User-Agent: Mutt/1.5.21 (2010-09-15) On Jun 21 03:26, Charles Wilson wrote: > The following statement: > > char * tmp_path = > (char *) cygwin_create_path (CCP_POSIX_TO_WIN_A, newargz[0]); > > Results in this error popup (and a coredump), when newargz[0] is > NULL. Sure, it's a bug in my program to do that...but shouldn't it > be handled more gracefully? Like...return a NULL, rather than > SIGABRT? I changed the underlying cygwin_conv_path to handle NULL gracefully by returning -1 and setting errno to EINVAL. This results in a NULL return from cygwin_create_path. HTH, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple