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: Jakub Jelinek <jakub at redhat dot com>
To: Roland McGrath <roland at redhat dot com>
Cc: Andreas Schwab <schwab at suse dot de>, 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 11:10:33 +0100
Subject: Re: [resend] memccpy() question
References: <jeu1dru5tv.fsf@sykes.suse.de> <200303251005.h2PA5Ge04684@magilla.sf.frob.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Tue, Mar 25, 2003 at 02:05:16AM -0800, Roland McGrath wrote:
> > 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.

And string/test-{mem,st}*.c test for the behaviour near the mapping end too,
just test-memccpy.c is not written (yet).

	Jakub

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

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