From:	Carsten DOT Roedel AT rt DOT bosch DOT de (Carsten Roedel K8/DIC2 Tel. 4276)
Subject:	Re: strlen on a NULL
13 May 1998 10:10:58 -0700 :
Message-ID:	<199805130614.IAA05154.cygnus.gnu-win32@dic.k8.rt.bosch.de>
To:	ian AT kiwiplan DOT co DOT nz, Kjeld DOT F DOT Christensen AT dxd DOT ericsson DOT se
Cc:	gnu-win32 AT cygnus DOT com

> 
> > If I do a strlen on a NULL pointer I get a coredump.
> > I have the same code running on a few *other* Unix machines with
> > exhibiting this behaviour.
> > OK, so I could tidy it up, but I wondered is this an oversight or the
> > correct behaviour?
> 
> I just observed the same problem.
> The differnce lies in where the core is located. A UNIX core starts from
> ZERO, and thus you are allowed to read from a NULL pointer on UNIX, as
> You read from your code.
> 
> On NT your process may lie anywhere, but never in ZERO, Thus you are not
> permitted to read from adress NULL. (You are not allowed to snoop around
> in the interrupt vetors!)
> 
> So this is the explanation!
>   
>   Kjeld
> 

I discovered the same behaviour, on most UNIX systems you'll receive a 
Signal (Bus Error e.g.). Better check all vectors before doing something
with them, like 'strlen'. By the way, in 'free' it's getting worse,
because you must also check not for pointing to a 'Zero', this causes a crash. 

:-)
Carsten
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -