This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior

From: Andreas Schwab <schwab at suse dot de>
To: "Florian Weimer \(Code Review\)" <gerrit at gnutoolchain-gerrit dot osci dot io>
Cc: libc-alpha at sourceware dot org, fweimer at redhat dot com
Date: Wed, 30 Oct 2019 11:44:04 +0100
Subject: Re: [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior
References: <gerrit.1572431114000.Ia3e68bc2d4d7e967df141702fb2f600cbd4a6432@gnutoolchain-gerrit.osci.io> <gerrit.1572431114000.Ia3e68bc2d4d7e967df141702fb2f600cbd4a6432@gnutoolchain-gerrit.osci.io>

On Okt 30 2019, Florian Weimer (Code Review) wrote:

> +Note that @var{s} must be an array of at least @var{maxlen} bytes.  It
> +is undefined to call @code{strnlen} on a shorter array, even if it is
> +known that the shorter array contains a null terminator.

This is not true.  strnlen _always_ stops before the null byte.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Follow-Ups:
- Re: [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior
  - From: Florian Weimer

References:
- [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior
  - From: Florian Weimer (Code Review)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]