On 10/27/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 10/26/06, Kenneth Porter <shiva@sewingwitch.com> wrote:
[snip]
> > The failure occurs in the memcmp (which is inlined with a REPE CMPS).
> > he->key (0xFAD6B8) is pointing to non-existent memory. It seems to be
> > pointing to just after the hash entry memory. (he is 0xFAB8D0.) The rest of
> > the hash entry looks sane (has correct hash value and key length). I'm
> > wondering if the key was prematurely freed and the page was released.
> >
> > I also chased the next pointer and looked at its key, and it has the same
> > issue. So the block holding the keys for this table seems to have been
> > released from VM.
>
> Could you possibly get a backtrace? The fact that the error occurs in
> the apr hash code is interesting, but in order for that information to
> be really useful we'd need to know which hash it's talking about, what
> is going on when it gets to this point, etc.
Even more helpful would be a reproduction recipe or at least the data
(and possibly the repository if it doesn't fail with a fresh one) that
causes the crash...is that possible?
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 27 17:33:35 2006