Re: glib memory allocation problems

[Miklos Szeredi <miklos szeredi hu>]

> > seems you managed to crash around the slice debugger doing realloc().
> > more interesting than the backtrace should actually be the
> > program output.
> > if you saw something like:
> >    GSlice: MemChecker: attempt to release block with invalid size...
> 
> I saw no such output on the last ~100 lines before the crash, that's
> why I took the backtrace...
> 
> > then you actually have something to fix.
> > if not, i suspect you have a bad memory corruption somewhere, e.g.
> > where you're writing into already released memory regoins.
> > that can cause crashes pretty much everywhere.

Hmm.  We did check for memory corruption with valgrind.  Maybe
valgrind didn't catch this one, because it's not aware of glib's
allocator.

Dimitrios, can you run your test with valgrind and with
G_SLICE=always-malloc?  Maybe that'll catch some corruption that
valgrind didn't catch with the g_slice allocator.

> the machine is memchecked/cpuchecked and no memory errors
> occur. Miklos, perhaps you figured out an sshfs bug on the latest
> backtraces?

No, the backtraces just show that there's memory corruption in glib's
allocator.  But there's no indication where this corruption could be
coming from.

Thanks,
Miklos