libc printf behaviour for NULL string [PSARC/2008/403 FastTrack timeout 07/02/2008]

[James Carlson]

Darren J Moffat writes:
> James Carlson wrote:
> > So, with this one under our belts, should we also fix up the str*(3C)
> > family of functions so that they quietly ignore NULL pointers as well?
> 
> The goal of this case was parity with the other mentioned libc 
> implementations.  I have looked at what the others do for strlen(NULL) 
> and they will SEGV on that.  I haven't looked at every str*(3C) function.

OK.  That's what I was looking for.  I did some searching, too, and
couldn't find str*(3C) functions that ignored NULL, but wasn't sure.
I wanted to know that hacking printf in this way was "complete" for
the applications that apparently need it.

> If the applicaiton/lib is that free and loose with NULL then we still 
> have the ability to LD_PRELOAD=0 at 0.so.1 if the code can't be fixed.

Sure, but that gets us right back to the original problem, which is
that they don't wanna.  ;-}

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677