Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 2 Jul 2002 20:21:39 -0400
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: segfault with bash / latest CVS cygwin1.dll
Message-ID: <20020703002139.GD8916@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <010c01c22200$37790e60$0100a8c0@advent02> <20020703000312.GA8916@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020703000312.GA8916@redhat.com>
User-Agent: Mutt/1.3.23.1i

On Tue, Jul 02, 2002 at 08:03:12PM -0400, Christopher Faylor wrote:
>On Tue, Jul 02, 2002 at 08:39:44PM +0100, Chris January wrote:
>>I am seeing a segfault with bash which appears to be due to a
>>fhandler_socket method being called on a NULL pointer.
>
>Should be fixed.  It was only tickled during a syscall_printf so it
>only occurred when run under strace.

Btw, thanks for the large amounts of debugging info.  It helped
*immensely* in fixing the problem.

cgf

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

