Bug#188677: libc6: Ionv doesn't accept NULL outbuf

[GOTO Masanori <gotom@debian.or.jp>]

At Sat, 19 Apr 2003 02:06:26 +0600 (YEKST),
Victor Porton wrote:
> 
> 
> On 18-Apr-2003 GOTO Masanori wrote:
> > At Tue, 15 Apr 2003 22:36:32 +0600 (YEKST),
> > Victor Porton wrote:
> >> On 15-Apr-2003 GOTO Masanori wrote:
> >> > At Sat, 12 Apr 2003 14:44:35 +0600 (YEKST),
> >> > Victor Porton wrote:
> >> >> Package: libc6
> >> >> Version: 2.3.1-16
> >> >> Severity: normal
> >> >> X-Debbugs-CC: bugs@gnu.org
> >> >> 
> >> >> iconv() with outbuf == NULL || *outbuf == NULL crashes despite of the
> >> >> libc.info file permits this case.
> >> > 
> >> > It seems libc.info should be needed to add the condition about outbuf
> >> > == NULL condition.  I plan to change libc.info, is it ok?
> >> 
> >> libc.info *already* says that outbuf==NULL is OK (however it forget to
> >> say
> >> about outbytesleft if outbuf==NULL), but in fact libc crashes if
> >> outbuf==NULL. 
> > 
> > Did you read iconv(3)?  outbuf == NULL && inbuf == NULL case is
> > acceptable, not outbut == NULL && inbuf != NULL.
> 
> I'm about libc.info, not about iconv(3).

Yes!  So I propose you that we should write this issue which is
similar to iconv(3) in the libc.info.

Regards,
-- gotom