Bug 148671 – dev-util/subversion 1.3.2-r3 / 1.4.0 segfaults on commit / import

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Fab 2006-09-22 09:59:41 UTC]

Hi,

I'm trying to use subversion 1.3.2-r3.
I did the following to create the repository :

 # svnadmin create /data/svn-repos/mesge
 # chown -R root:svnusers /data/svn-repos/mesge
 # chmod -R g-w /data/svn-repos/mesge
 # chmod -R g+rw /data/svn-repos/mesge/db
 # chmod -R g+rw /data/svn-repos/mesge/locks


Everything is ok. My user is in the svnusers group, I ran :

 $ svn co file:///data/svn-repos/mesge/

Then I copy/paste the 'trunk' folder in the extracted revision 0 folder, and :

 $ svn add trunk
 $ svn commit
Segfault



I tried to upgrade to subversion-1.4.0, same issue.
I tried the 'import' command, same issue.

Did I miss something ?
I'll attach emerge --info, and strace of each command.

Thanks.

[Comment 1 Fab 2006-09-22 10:01:04 UTC]

Created attachment 97763 [details]
emerge --info

[Comment 2 Fab 2006-09-22 10:02:19 UTC]

Created attachment 97764 [details]
svn commit strace

[Comment 3 Fab 2006-09-22 10:03:00 UTC]

Created attachment 97765 [details]
svn import strace

[Comment 4 Paul de Vrieze (RETIRED) 2006-09-23 07:54:37 UTC]

Did you actually get an editor to give the commit/import message. I can't really see what went wrong. It should work just fine. As an experiment you might want to create the repository as a user and leave other things alone. This however should not make a difference.

[Comment 5 Fab 2006-09-23 08:08:30 UTC]

(In reply to comment #4)
> Did you actually get an editor to give the commit/import message.

Yes, I'm using vim. But even when I'm trying this command :

 $ svn commit -m 'first commit'

Issue is the same : segfaults.

> As an experiment you might want to create the repository as a user and leave other things alone.

I'll give it a try.


Additionally, I tried with 1.3.2-r1, and segfaults are also here, I don't understand. I think I'll try to rebuild dependencies.

[Comment 6 Fab 2006-09-23 12:05:22 UTC]

> As an experiment you might want to create the repository as a user and leave
> other things alone. This however should not make a difference.

I tried and it change nothing.


But I found the solution. I ran :

 $ gdb --args svn commit -m 'first commit'

gdb told me something about libapr-0.so.0 near around the segfault.
So, I ran :

 # emerge --oneshot $(equery which libapr-0.so.0)

And I retried ==> segfaults.
Then I decided to rebuild subversion-1.4.0 like the following to see what's going on :

 # FEATURES="nostrip" emerge subversion

And, fortunately, after rebuilding subversion, the segfault has disappeared !
Now it seems to work fine. Anyway, thanks for your help.

[Comment 7 Fab 2006-09-23 12:06:41 UTC]

mmmmh, not 'equery which' but 'equery belongs' :-)