Subject: Re: tgetstr bug
To: None <>
From: Valeriy E. Ushakov <>
List: tech-userlevel
Date: 12/17/2006 09:34:39
Christos Zoulas <> wrote:

> In article <>,
> Bruno Haible  <> wrote:
>>tgetstr ("md", NULL) crashes on NetBSD. It's here:
>>char *
>>t_getstr(struct tinfo *info, const char *id, char **area, size_t *limit)
>>                _DIAGASSERT(limit != NULL);
>>                *limit = i;                    <=====
>>                free(s);
>>                return NULL;
>>Other systems support tgetstr ("md", NULL) without problems, and
>>return the string in a statically allocated buffer.
> The code that passes NULL is non-portable. According to the TOG:
>    The tgetstr() function gets the string entry for id. If area is
>    not a null pointer and does not point to a null pointer, tgetstr()
>    copies the string entry into the buffer pointed to by *area and
>    advances the variable pointed to by area to the first byte after
>    the copy of the string entry.
> By making tgetstr(id, NULL) work, we are encouraging non-portable
> behavior.

Hmm, why is that non-portable?  I read TOG text as that tgetstr
returns the capability *and*, if area is not null, also copies the
capability string into the area.

Do I miss something?

SY, Uwe
--                         |       Zu Grunde kommen          |       Ist zu Grunde gehen