On Wed, Apr 23, 2008 at 2:11 AM, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 22, 2008 at 11:50 PM, Mike Meyer <[EMAIL PROTECTED]> wrote: > > > On Tue, 22 Apr 2008 22:40:21 -0700 > > "Garrett Cooper" <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > I made an oops in a program, which uncovered "feature" in > > strdup(2) > > > that I wasn't aware of before. So I was wondering, is strdup(pointer = > > NULL) > > > supposed to segfault should this just return NULL and set errno? > > > > Yes, it's supposed to segfault. Check out what, say, strcpy does if > > you ask it to copy a NULL pointer. And this is an improvement from the > > bad old days, when they would happily walk through memory starting at > > 0..... > > > > Besides, errno is used to signal errors from system calls. strdup > > isn't a system call, it's a library function (says so at the top of > > the man page). > > > > > Good news is that Linux does the same thing (yay?), so at least > > FreeBSD > > > isn't alone.. > > > > Do you have examples of systems where strdup doesn't behave this way? > > > > <mike > > > No, I don't, but then again I just noticed this. > -Garrett > (and thanks for clarifying about errno; didn't realize that) -Garrett _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
