On Sun, 9 Apr 2006, Jeremy Allison wrote:
> On Sun, Apr 09, 2006 at 10:10:07AM -0700, Terry Hardie wrote:
> > On Sun, 9 Apr 2006, Terry Hardie wrote:
> >
> > > On Sun, 9 Apr 2006, Terry Hardie wrote:
> > >
> > > > > Ok, seems ok as far as I kno
On Sun, 9 Apr 2006, Terry Hardie wrote:
> On Sun, 9 Apr 2006, Terry Hardie wrote:
>
> > > Ok, seems ok as far as I know. If this is reproducible
> > > for you you might want to try setting MALLOC_CHECK_=2
> > > before running smbd, or if you can reproduce it w
On Sun, 9 Apr 2006, Terry Hardie wrote:
> > Ok, seems ok as far as I know. If this is reproducible
> > for you you might want to try setting MALLOC_CHECK_=2
> > before running smbd, or if you can reproduce it with
> > one client use valgrind.
>
> This is what I get
On Fri, 7 Apr 2006, Jeremy Allison wrote:
> On Thu, Apr 06, 2006 at 11:23:32PM -0700, Terry Hardie wrote:
> > On Thu, 6 Apr 2006, Jeremy Allison wrote:
> >
> > > On Thu, Apr 06, 2006 at 09:00:49PM -0700, Terry Hardie wrote:
> > > > On T
On Thu, 6 Apr 2006, Jeremy Allison wrote:
> On Thu, Apr 06, 2006 at 09:00:49PM -0700, Terry Hardie wrote:
> > On Thu, 6 Apr 2006, Jeremy Allison wrote:
> > >
> > > What OS are you running Samba on ? The directory code is very
> > > different between 3.0.
On Thu, 6 Apr 2006, Jeremy Allison wrote:
> On Wed, Apr 05, 2006 at 03:55:56PM -0700, Terry Hardie wrote:
> > Hi,
> >
> > I'm running samba 3.0.22, and have reproduced this issue in 3.0.14a as
> > well. I am trying to access a network share with a large number of
howing up:
*** glibc detected *** free(): invalid pointer: 0xb7edbc38 ***
I've seen a few other people complaining about this. I've tried the
backup/verify of the .tdb's - didn't find any problems. I've also tried
upding my glibc to the latest
howing up:
*** glibc detected *** free(): invalid pointer: 0xb7edbc38 ***
I've seen a few other people complaining about this. I've tried the
backup/verify of the .tdb's - didn't find any problems. I've also tried
upding my glibc to the lates
