Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!ames!umd5!uvaarpa!mcnc!rti!xyzzy!meissner
From: meissner@xyzzy.UUCP (Michael Meissner)
Newsgroups: comp.unix.wizards
Subject: Re: Speaking of ksh
Message-ID: <894@xyzzy.UUCP>
Date: 3 Jun 88 12:35:00 GMT
Article-I.D.: xyzzy.894
References: <300@hi3.aca.mcc.com.UUCP>
Reply-To: meissner@xyzzy.UUCP (Michael Meissner)
Organization: Data General (Languages @ Research Triangle Park, NC.)
Lines: 22

In article <300@hi3.aca.mcc.com.UUCP> ables@hi3.aca.mcc.com.UUCP (King Ables)
writes:

	(summary of converting ksh to use getpwnam deleted)

| Ksh seems to have its own malloc(), free(), and _filbuf()
| which I have renamed everywhere within ksh, but the problem
| hasn't gone away.  I was thinking a duplicate entry point
| would explain the problem, but I think I've elminiated them.
| I now thin something somewhere is overwriting something.

At Data General, we discovered that the internals of the YP stuff
depend on either malloc(0) returning a useable pointer, or that NULL
is an acceptable user address.

In a similar note, I wish that programs would stop replacing
internals of the library, or at least make it an option to
use the default routines.
-- 
Michael Meissner, Data General.

Uucp:	...!mcnc!rti!xyzzy!meissner
Arpa:	meissner@dg-rtp.DG.COM   (or) meissner%dg-rtp.DG.COM@relay.cs.net