[SVN-792] Nasty commit bug.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: all
• Fix Version/s: 0.14.0
• Component/s: src

Environment

Linux

• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 13/Jul/02 03:54
• Updated: 27/Oct/18 16:39
• Resolved: 15/Sep/04 08:43

Description

Here's the deal.

I committed a revision, which segfaulted after transmitting the data to the
server.  I didn't manage to grab a backtrace of it.  I then committed a second
revision, which also segfaulted, AND more importantly, corrupted the data in
the repository.

The best guess at this point is that the first segfault happened in such a way
that the entries file had been updated, but the new text-base hadn't been
created yet.  The output of svn diff seems to confirm this as the delta seems
to include both sets of changes.

A backtrace, history log, and some svn st and svn diff output are located on
the dev list mail in a thread with the subject "nasty commit bug"

I'm also about to create an attachment to this issue containing a tarred up
version of my working copy.

Original issue reported by kevin

Issue Links

• duplicates: SVN-797 ra_dav can fail to detect file out-of-dateness