This is the mail archive of the 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]

[Bug manual/19406] New: memchr description: may it access all @var{size} bytes?

            Bug ID: 19406
           Summary: memchr description: may it access all @var{size}
           Product: glibc
           Version: 2.22
            Status: NEW
          Severity: normal
          Priority: P2
         Component: manual
          Assignee: unassigned at sourceware dot org
          Reporter: cherepan at mccme dot ru
                CC: mtk.manpages at gmail dot com, roland at gnu dot org
  Target Milestone: ---

The description of the memchr function in C11,, says that memchr
cannot access the part of the array after the located char:

"The implementation shall behave as if it reads the characters sequentially and
stops as soon as a matching character is found."

The glibc manual doesn't provide this guarantee:

"This function finds the first occurrence of the byte @var{c} (converted to an
@code{unsigned char}) in the initial @var{size} bytes of the object beginning
at @var{block}.  The return value is a pointer to the located byte, or a null
pointer if no match was found.";a=blob;f=manual/string.texi;h=016fd0b9a05f3126a1594e942c5e6da0669d0410;hb=HEAD#l1716

The implementation is probably fine so only the manual is wrong.

You are receiving this mail because:
You are on the CC list for the bug.

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