Re: coredump completing scp

[Bart Schaefer <schaefer@brasslantern.com>]

On Jan 29, 10:16pm, Peter Stephenson wrote:
}
} Vin Shelton wrote:
} > Thanks for the suggestion.  Here's the report from valgrind.  The call
} > to setpwent is made from fillnameddirtable in hahstable.c.  I don't
} > really know what else to make of this, though.
} 
} Me neither, I'm afraid.  It certainly *looks* like an error within
} setpwent itself, though that doesn't necesarily mean it is.  As valgrind
} is claiming the memory wasn't malloc'd at all it doesn't give us much of
} a lead.

This sure seems like a bug in setpwent(), but I'll note that we're making
a call to setpwent() before ever calling getpwent() in the first place.
The doc says:

   The setpwent() function effectively rewinds the user database to allow
   repeated searches.

It may be that setpwent() assumes that getpwent() has allocated something
that it needs to free, something which never has been allocated because
getpwent() has never been called?  And that only the zsh-mem free() has
a problem with this?