On Fri, Jul 12, 2002 at 11:35:26PM -0400, Kevin Pilch-Bisson wrote:
> Okay I'm home, and I have some more info to pass along.
>
> 1. I actually had 2 segfaults after commits today. The first one didn't
> seem to have an affect on the commit.
>
> 2. My guess is that the first segfault is the cause of the problem, exactly
> as Ben described elsewhere. entries file thinks its at the new rev, but
> text-base isn't.
>
> 3. For reference, here is part of my 'history' output with commentary.
>
> 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 . -
svn_wc_process_committed segfaults as locked_dirs doesn't have a
lock in the hashtable. My caching patch changed the lock_dir API
to handle this case explicitly. =)
Fix coming.
I'll see if I can reproduce the second segfault. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 13 07:35:59 2002