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, 29 Nov 2002 12:38:46 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Samba Client compilation on the latest DLL
Message-ID: <20021129173846.GA22545@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <2628 DOT 193 DOT 132 DOT 197 DOT 91 DOT 1038574382 DOT squirrel AT mail DOT iseekuk DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021129081339 DOT 02755ec0 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20021129081339.02755ec0@pop3.cris.com>
User-Agent: Mutt/1.5.1i

On Fri, Nov 29, 2002 at 08:15:57AM -0800, Randall R Schulz wrote:
>Have you checked to verify that all the declarations of the suspect global 
>data are consistent with its definition?

Yes.  What Randall is effectively saying is that contrary to popular
opinion on the cygwin mailing list, every segv is not a cygwin problem.
You should exercise standard programming practice and *debug* your program
before blaming the problem on cygwin.  Expecting that someone will have
a magical solution to a simple SEGV is asking a lot.  It should be really
really obvious that something as simple as the code snippet posted is
going to work without problem.  If it didn't then the mailing list would
be filled with complaints.

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/