Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<00b801c1ba85$91ee1300$0100a8c0@mshome.net>
From:	"bowman" <bowman AT montana DOT com>
To:	<cygwin-developers AT cygwin DOT com>
References:	<01c901c1ba5b$e3dee330$0200a8c0 AT lifelesswks> <20020220222124 DOT GD3196 AT redhat DOT com> <3C7426A3 DOT 2FDF07F2 AT yahoo DOT com>
Subject:	Re: null parameters to functions
Date:	Wed, 20 Feb 2002 20:12:16 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

From: "Earnie Boyd" <earnie_boyd AT yahoo DOT com>
>
> IIRC, it's not an error in Linux land or most *nixes for that matter.
> It OS dependent on how addressing a null pointer is handled.  Looking at
> the man page from HPUX 11 it says that null pointer values are treated
> as empty strings.

AIX4 ignores NULL, but most of the Linux platforms will dump core on an
attempt to access NULL. We've been developing on Linux for some time, and
catch errors that our AIX4 legacy code calmly ignored.

I think the behavior can be configured, but the default is to die for any
Linux box I've worked on.

- Raw text -