[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: nasty commit bug

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-07-13 19:32:59 CEST

Blair Zajac <blair@orcaware.com> writes:

> Philip Martin wrote:
> >
> > Justin Erenkrantz <jerenkrantz@apache.org> writes:
> >
> > > > 664 svn ci -F log include/svn_wc.h include/svn_error_codes.h
> > > > libsvn_wc/props.c libsvn_client/prop_commands.c
> > > > *** I CTRL-C'd this for some reason before any output.
> > > > 665 cat log
> > > > 666 svn ci -F log include/svn_wc.h include/svn_error_codes.h
> > > > libsvn_wc/props.c libsvn_client/prop_commands.c
> > > > *** This segfaulted, but created a valid new revision.
> > >
> > > The segfault can be reproduced by commiting without anything in . -
> >
> > Can you give me a reproduction recipe? I still can't make it fail.
>
> Here's one:
>
> svnadmin create z
> cp -p z/hooks/post-commit.tmpl z/hooks/post-commit
> svn co file:///`pwd`/z -d zz
> cd zz
> svn mkdir a
> svn ci -F /dev/null
>
> Do not put executable permissions on z/hooks/post-commit.

I don't think that's the one that caused the NULL adm_access_t
segfault. Neither of Kevin's segfaults can have been caused by your
use case. I want to see the segfault that got fixed by rev 2504. The
one that "can be reproduced by commiting without anything in ."

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 13 19:54:03 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.