This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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: [resend] memccpy() question

From: Roland McGrath <roland at redhat dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: Jes Sorensen <jes at trained-monkey dot org>,libc-hacker at sources dot redhat dot com, srn at sgi dot com
Date: Tue, 25 Mar 2003 02:05:16 -0800
Subject: Re: [resend] memccpy() question

> From the POSIX description:
> 
>     The memccpy() function shall copy bytes from memory area s2 into s1,
>     stopping after the first occurrence of byte c (converted to an
>     unsigned char) is copied, or after n bytes are copied, whichever comes
>     first.
> 
> I'd conclude that memccpy must not touch the memory after the character.

I concur.  Note that we have string/stratcliff.c to test exactly this kind
of issue for some other string functions.  It seems appropriate to test
memccpy there too.

Follow-Ups:
- Re: [resend] memccpy() question
  - From: Jakub Jelinek

References:
- Re: [resend] memccpy() question
  - From: Andreas Schwab

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