PRoblem while importing CVS repository to svn
Balkar Pa <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I am trying to import the CVS repository to SVN using the cvs2svn-2.3.0. I
am just trying to smple import with all the history from the CVS. Here is
the details:
cvs2svn-2.3.0
Python 2.6.2 (r262:71600, Jan 19 2010, 13:59:36)
[GCC 3.4.3 (csl-sol210-3_4-branch+sol_rpath)] on sunos5
Command:- cvs2svn --dumpfile=/disk1/bcakup/cvs/svn.dmp
--fallback-encoding=utf_8 /disk2/backup/cvs/cvsdir
This command gets executed till the last pass and
then I get a core dump. Here is the log:
----- pass 16 (OutputPass) -----
Starting Subversion Dumpfile.
Bus Error (core dumped)
Command:- cvs2svn --dumpfile=/disk1/bcakup/cvs/svn.dmp
--fallback-encoding=utf_8 -p OutputPass /disk2/backup/cvs/cvsdir
Similarly if I try to resume from where the error happened, same error i
get.
Here is the output from core dump.
-bash-3.00$ pstack core
core 'core' of 23975: /usr/local/bin/python /usr/local/bin/cvs2svn
--dumpfile=/disk1/bcakup/
fe99c1d4 __mutex_alloc_int (cfc600, 0, 13, 8, ffbfdcfc, cfc990) + b4
fe99cd58 __mutex_open (0, 284504, 1, 1, ffff66d0, 0) + 178
fe9d9ce0 __env_open (0, 578118, 1145, 573460, fe9da1e4, 0) + 24c
fea808dc DBEnv_open (dd76b0, 52e198, 0, 117400, 117820, feaa1d68) + 78
00117844 PyCFunction_Call (50b918, 52e198, dd76b0, 52e1a0, 4, 1cdee0) + 114
000b11f0 PyEval_EvalFrameEx (cfc5e0, ffbfdf54, 3e3f50, 1, 52e198, 1db3e4) +
5ccc
000b21c8 PyEval_EvalFrameEx (1679ac, ffbfe074, 3e3da0, 1, 1, 3e27c8) + 6ca4
000b2bb0 PyEval_EvalCodeEx (3e3da0, 1e3, 6, 1e4, 3, 24) + 754
000b1174 PyEval_EvalFrameEx (cfc184, ffbfe224, 3db020, 1, 3, 3e0140) + 5c50
000b2bb0 PyEval_EvalCodeEx (3db020, 3b5328, 4, cfecc4, 3, cfecd0) + 754
000b1174 PyEval_EvalFrameEx (cfecd0, ffbfe3d4, 3d6f50, 1, 3, 1a4440) + 5c50
000b2bb0 PyEval_EvalCodeEx (3d6f50, 1, 29, 2, 2, c) + 754
000b1174 PyEval_EvalFrameEx (d099fc, ffbfe584, 3cfd58, 1, 2, 1a4440) + 5c50
000b2bb0 PyEval_EvalCodeEx (3cfd58, 83e468, 4, 1bf5ac, 4, 0) + 754
00117058 function_call (3d5bb0, 1bf5a0, 0, c, d, 3e8) + 88
000294c8 PyObject_Call (3d5bb0, 1bf5a0, 0, 1bf5a8, 3, 83e468) + 64
00034f00 instancemethod_call (0, 1bf5a0, 0, b, c, 3e8) + 94
000294c8 PyObject_Call (2c5f30, 48efd0, 0, 2, 1, 16b348) + 64
000aa680 PyEval_CallObjectWithKeywords (2c5f30, 48efd0, 0, e51eb, 2,
ffffffff) + 5c
0002ddcc PyInstance_New (2c5f30, 48efd0, 0, a, b, 3e8) + 84
000294c8 PyObject_Call (3efcf0, 48efd0, 0, 48efd8, d05564, 189000) + 64
000af578 PyEval_EvalFrameEx (d05560, ffbfec6c, 485338, 1, 0, 235318) + 4054
000b21c8 PyEval_EvalFrameEx (529150, ffbfed8c, 37f890, 1, 1, 1ac440) + 6ca4
000b2bb0 PyEval_EvalCodeEx (37f890, 5772e4, 5, 52b85c, 2, 0) + 754
00117058 function_call (478b70, 52b850, 0, 7, 8, 3e8) + 88
000294c8 PyObject_Call (478b70, 52b850, 0, 3fc00, 478b70, ffffffff) + 64
00034f00 instancemethod_call (2, 52b850, 0, 6, 7, 3e8) + 94
000294c8 PyObject_Call (2c5e68, 52b850, 0, 52b858, 5864ac, 189000) + 64
000af578 PyEval_EvalFrameEx (5864a8, ffbff31c, 38a410, 1, 0, 37de20) + 4054
000b21c8 PyEval_EvalFrameEx (5772e4, ffbff43c, 4a5ec0, 1, 2, 3282a0) + 6ca4
000b21c8 PyEval_EvalFrameEx (52e800, ffbff55c, 3242f0, 1, 3, 29b440) + 6ca4
000b21c8 PyEval_EvalFrameEx (49a710, ffbff67c, 1c54e8, 1, 2, 29b440) + 6ca4
000b21c8 PyEval_EvalFrameEx (2ac2d8, ffbff79c, 213608, 1, 3, 1be420) + 6ca4
000b21c8 PyEval_EvalFrameEx (4f05d0, ffbff8bc, 20ecc8, 1, 2, 0) + 6ca4
000b2bb0 PyEval_EvalCodeEx (20ecc8, 1b8270, 1b8270, 0, 0, 0) + 754
000b2d70 PyEval_EvalCode (20ecc8, 1b8270, 1b8270, 1, ff0e8284, 0) + 28
000d8ea0 PyRun_FileExFlags (0, ffbffd92, 1a0128, 1b8270, 1b8270, 1) + 10c
000d9dec PyRun_SimpleFileExFlags (f2d1, ffbffd92, 1, ffbffba4, ff0e8284,
ff0ecb40) + bc
0001f654 Py_Main (ffffffff, ffbffcb4, 4000, 1943d8, 194000, 1) + 8dc
0001e8c8 _start (0, 0, 0, 0, 0, 0) + 5c
Any body has run into any similar issues?
Regards,
bp
------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2441068
To unsubscribe from this discussion, e-mail: [[email protected]].