Re: strncpy is not a safe version of strcpy

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: strncpy is not a safe version of strcpy
Дата
Msg-id 20131115150412.GC17272@tamriel.snowman.net
обсуждение исходный текст
Ответ на Re: strncpy is not a safe version of strcpy  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: strncpy is not a safe version of strcpy  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
* Andres Freund (andres@2ndquadrant.com) wrote:
> Sure, there can be longer paths, but postgres don't support them. In a
> *myriad* of places. It's just not worth spending code on it.
>
> Just about any of the places that use MAXPGPATH are "vulnerable" or
> produce confusing error messages if it's exceeded. And there are about
> zero complaints about it.

Confusing error messages are one thing, segfaulting is another.
Thanks,
    Stephen

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: strncpy is not a safe version of strcpy
Следующее
От: Andres Freund
Дата:
Сообщение: Re: strncpy is not a safe version of strcpy