git svn fetch segfaults

DISCUSSION Dennis Schridde 4 participants 7 messages Jun 15, 2016

lore

Share & tools

lore

Dennis Schridde

author

2016-06-15 22:44 UTC #0 lore raw

Hello!

The following procedure results in a segfault:

mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch

A full log is attached.
If you want any more information, a dump of the SVN repository, etc, just tell me.

The last part which seems to be interesting is this one:

Odd number of elements in anonymous hash at /usr/bin/git-svn line 1760. r13 = 7f00bbc9c92e5601b158c2cbc572b8e7bdcebe59 (tags/1.10a) Segmentation fault

If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.

(Note that in the other mail, where I reported about the "Odd number of elements" problem, I used "git svn clone" instead.)

I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2

--Dennis

(Please CC me if you answer, since I am not subscribed.)

Miklos Vajna

2016-06-15 22:44 UTC #1 lore raw

Quoted 6 lines · Dennis Schridde

mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch

wget http://svn.kynes.de/warzone2100.bz2

svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load warzone2100

the rest is the same i get a segfault at the very same place.

Quoted 2 lines

If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.

same.

Quoted 3 lines

I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2

$ svn --version
svn, version 1.4.5 (r25188)

$ git --version
git version 1.5.4.rc2.38.gd6da3

thanks,
- VMiklos

Dennis Schridde

author

2016-06-15 22:44 UTC #2 lore raw

Am Mittwoch, 9. Januar 2008 01:33:07 schrieb Miklos Vajna:

Quoted 1 line

On Tue, Jan 08, 2008 at 11:25:45PM +0100, Dennis Schridde

Quoted 23 lines · <[email protected]> wrote:

Quoted 6 lines
mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch
wget http://svn.kynes.de/warzone2100.bz2
svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load warzone2100
the rest is the same i get a segfault at the very same place.
Quoted 2 lines
If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.
same.
Quoted 3 lines
I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2

Quoted 5 lines

$ svn --version
svn, version 1.4.5 (r25188)

$ git --version
git version 1.5.4.rc2.38.gd6da3

Same with git version 1.5.3.7

Junio C Hamano

2016-06-15 22:44 UTC #3 lore raw

Quoted 26 lines · Dennis Schridde

Am Mittwoch, 9. Januar 2008 01:33:07 schrieb Miklos Vajna:
Quoted 1 line
On Tue, Jan 08, 2008 at 11:25:45PM +0100, Dennis Schridde
Quoted 23 lines · <[email protected]> wrote:
Quoted 6 lines
mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch
wget http://svn.kynes.de/warzone2100.bz2
svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load warzone2100
the rest is the same i get a segfault at the very same place.
Quoted 2 lines
If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.
same.
Quoted 3 lines
I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2

Quoted 6 lines

Quoted 5 lines
$ svn --version
svn, version 1.4.5 (r25188)
$ git --version
git version 1.5.4.rc2.38.gd6da3
Same with git version 1.5.3.7

Has anybody determined which executable is the segfaulting one?

If it is svn executable spawned by Perl that runs git-svn, or libsvn shared object linked to Perl while running git-svn, I suspect testing with different git versions will not be very productive.

Björn Steinbrink

2016-06-15 22:44 UTC #4 lore raw

Quoted 28 lines · Junio C Hamano

Quoted 26 lines · Dennis Schridde
Am Mittwoch, 9. Januar 2008 01:33:07 schrieb Miklos Vajna:
Quoted 1 line
On Tue, Jan 08, 2008 at 11:25:45PM +0100, Dennis Schridde
Quoted 23 lines · <[email protected]> wrote:
Quoted 6 lines
mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch
wget http://svn.kynes.de/warzone2100.bz2
svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load warzone2100
the rest is the same i get a segfault at the very same place.
Quoted 2 lines
If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.
same.
Quoted 3 lines
I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2

Quoted 8 lines

Quoted 6 lines
Quoted 5 lines
$ svn --version
svn, version 1.4.5 (r25188)
$ git --version
git version 1.5.4.rc2.38.gd6da3
Same with git version 1.5.3.7
Has anybody determined which executable is the segfaulting one?

I just tried to, but it's still running, at r600 now.

Quoted 4 lines

If it is svn executable spawned by Perl that runs git-svn, or libsvn shared object linked to Perl while running git-svn, I suspect testing with different git versions will not be very productive.

Oh well, anyway, just for the record:
doener@atjola:~ $ svn --version
svn, version 1.4.4 (r25188)

doener@atjola:~ $ git --version
git version 1.5.4.rc1.11.gd2f82

Björn

Björn Steinbrink

2016-06-15 22:44 UTC #5 lore raw

Quoted 32 lines · Björn Steinbrink

Quoted 31 lines · Junio C Hamano
Quoted 29 lines · Dennis Schridde
Am Mittwoch, 9. Januar 2008 01:33:07 schrieb Miklos Vajna:
Quoted 1 line
On Tue, Jan 08, 2008 at 11:25:45PM +0100, Dennis Schridde
Quoted 26 lines · <[email protected]> wrote:
Quoted 6 lines
mkdir org.gna.warzone2100.git
cd org.gna.warzone2100.git
git --bare init
git --bare svn init --use-svnsync-props --stdlayout file:///var/svn/warzone2100/
git --bare svn fetch
wget http://svn.kynes.de/warzone2100.bz2
svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load warzone2100
the rest is the same i get a segfault at the very same place.
Quoted 2 lines
If I do not specify --use-svnsync-prop to "git svn init", it gets past r13 in tags/1.10a.
same.
Quoted 3 lines
I am using these versions:
svn, version 1.4.6 (r28521)
git version 1.5.4.rc2
$ svn --version
svn, version 1.4.5 (r25188)

Quoted 7 lines

Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
$ git --version
git version 1.5.4.rc2.38.gd6da3
Same with git version 1.5.3.7
Has anybody determined which executable is the segfaulting one?
I just tried to, but it's still running, at r600 now.

It finished by now, no segfault with --use-svnsync-props.

Björn

Dennis Schridde

author

2016-06-15 22:44 UTC #6 lore raw

In reply to Junio C Hamano

Replying to this, as I haven't recieved the newer mail. (Not subscribed.) Handcopied the text, hope I didn't forgot anything.

Quoted 9 lines

Quoted 9 lines
Quoted 1 line
Has anybody determined which executable is the segfaulting one?
I just tried to, but it's still running, at r600 now.
Quoted 4 lines
If it is svn executable spawned by Perl that runs git-svn, or libsvn shared object linked to Perl while running git-svn, I suspect testing with different git versions will not be very productive.

Quoted 8 lines

Quoted 6 lines
Oh well, anyway, just for the record:
doener@atjola:~ $ svn --version
svn, version 1.4.4 (r25188)
doener@atjola:~ $ git --version
git version 1.5.4.rc1.11.gd2f82
It finished by now, no segfault with --use-svnsync-props.

For me it always segfaulted at r13 in tags/1.10a.
I crosses r13 before that already (trunk), but doesn't crash there.

I am now recompiling svn,git,perl to create a coredump, will the rerun it and hopefully get some backtraces from the dump.

Btw, I am running perl 5.8.8, in case that matters somehow.

--Dennis