Re: ls aborts due to free()ing an invalid pointer

[Steven Schlansker <stevenschlansker@calmail.berkeley.edu>]

Sjoerd Hiemstra wrote:
> Steven Schlansker wrote:
> > Sjoerd Hiemstra wrote:
> > > > > > On Wed, May 02, 2007 at 11:23:21AM -0700, Steven Schlansker
> > > > > > wrote:
> > > > > > > I'm having a rather strange error while trying to ls a large
> > > > > > > directory. The setup is as follows:
> > > > > > >
> > > > > > > /home is nfs-mounted from a BSD box
> > > > > > > nsswitch is set to use LDAP for passwd, shadow, and group info
> > > > > > > nscd is running to cache the responses from LDAP
> > > > > > >
> > > > > > > I try to run ls -l /home, and get the error
> > > > > > >
> > > > > > > steven@soda:~$ ls -l /home
> > > > > > > *** glibc detected *** free(): invalid pointer: 0xa7f9ad38 ***
> > > > > > > Aborted
> > > I'm seeing this same error in Etch, using xhfs to open a hfs
> > > formatted volume. In Sarge it works OK, with the same version of
> > > xhfs.
> > >
> > > I am under the impression that glibc broke something between version
> > > 2.3.2 (in Sarge) and 2.3.6 (which Etch has).
> > Are you also using LDAP for username lookups?
>
> Alas, I am not such an expert that I even know what LDAP is, or what
> username lookups are.  So, probably not.


In that case, it seems that there might be a glibc-related bug not 
having to do with LDAP?  Debugging this is way out of my league, though :/