RE: The smoking gun? was: make check failing on log_tests.py

> From: Philip Martin [mailto:philip@codematters.co.uk]
> Sent: 17 December 2001 13:37

> "Sander Striker" <striker@apache.org> writes:
>
> > Ofcourse we tried to reproduce this behaviour (wanting to rule out the
> > pools bug). I failed, Justin succeeded.
>
> Revision 631 passes the log tests, revision 632 fails. Now this may be
> coincidence, it is possible that the memory overwrite is just moving
> around and also exists in rev 631. However rev 632 says
>
> > Log:
> > Part III of the New Commit System - the conversion of ra_local. More
> > to follow.
>
> so it certainly affects the code that is failing.

Err, the latest apr (with new pools) doesn't play nice with the test
code before rev 647 of subversion. You should be seeing segfaults,
just like cmpilato had before he fixed subversions pools.
Or are you using an old apr against the earlier revisions?
 
> --
> Philip

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006