bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: some ftpd implementations mishandle CWD ~{


From: Andreas Jaeger
Subject: Re: some ftpd implementations mishandle CWD ~{
Date: 25 Apr 2001 08:45:48 +0200
User-agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.1 (Channel Islands)

Gregory A Lundberg <address@hidden> writes:

> Your patch to wu-ftpd looks fine.  Setting a known-null pointer to NULL is
> not needed, but otherwise I'll commit what you submitted.
> 
> If we free() a NULL pointer and that causes problems, that's not our
> problem.  The specification for free() specifically says "if ptr is a null
> pointer, no action occurs."  So the fact that a segmentation fault occurs
> on Linux indicates a non-compliance in the GNU libc runtime.  If that
> non-compliance causes down-stream problems by overwriting random memory,
> the best place to fix it is to bring free() into compliance.

free (NULL) works fine for glibc - we're following the standards.  But
what not works is:

ptr = malloc (1000);
free (ptr);
free (ptr);

A double free is not allowed.

Since you don't explain the problem in more detail, I don't know
what's going on in wu-ftpd and can't comment any better.  Please
supply more details.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj



reply via email to

[Prev in Thread] Current Thread [Next in Thread]