svn 1.8.1: segmentation fault on merge

[John Jacobson <et...@gmail.com>]

I am encountering the crash described below when doing a particular merge.
I've tried the merge on a clean checkout - it still segfaults. The same
merge succeeds with svn 1.7.8. What are the steps that I should take in
order to file a meaningful issue report?



$ svn merge ^/offline/asmm/branches/uat/Production --verbose
--- Merging
*Segmentation fault*


$ svn info .
Path: .
Working Copy Root Path: <redacted>
URL: <redacted>
Relative URL: ^/offline/asmm/trunk/Production
Repository Root: <redacted>
Repository UUID: 3c33d142-4166-11dd-ac8f-de326a75b49c
Revision: 180446
Node Kind: directory
Schedule: normal


$ svn info ^/offline/asmm/branches/uat/Production
Path: Production
URL: <redacted>
Relative URL: ^/offline/asmm/branches/uat/Production
Repository Root: svn://etgsvn/etg
Repository UUID: 3c33d142-4166-11dd-ac8f-de326a75b49c
Revision: 180449
Node Kind: directory

(Compiled & running on CentOS 6.2)
$ svn --version
svn, version 1.8.1 (r1503906)
   compiled Aug 16 2013, 14:07:12 on x86_64-unknown-linux-gnu

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme

Re: svn 1.8.1: segmentation fault on merge

[Ben Reser <be...@reser.org>]

On Tue Aug 20 08:09:02 2013, John Jacobson wrote:
> I am encountering the crash described below when doing a particular
> merge. I've tried the merge on a clean checkout - it still segfaults.
> The same merge succeeds with svn 1.7.8. What are the steps that I
> should take in order to file a meaningful issue report?

If you're able to build from source the best report can be to build 
Subversion by passing --enable-maintainer-mode to configure and then 
running the merge via gdb.  You don't need to install the version with 
debugging symbols to do this (just configure and make).

The following should do the trick (where BUILDDIR is where you built 
subversion):
libtool e gdb --args $BUILDDIR/subversion/svn/svn merge 
^/offline/asmm/branches/uat/Production --verbose

After gdb starts type r and press enter.

You should get a backtrace when the segfault happens.  Post the 
backtrace here.

That is going to be the best way.  If you can't do that you're probably 
going to have to try and describe the changes that are being merged.  
If you can find a way to reproduce it from a fresh repo with minimal 
steps that's even better.