cmpilato@collab.net writes:
> This is the second hint I've gotten that something is wrong with the
> svn_fs_node_created_rev function. The created revision as 25 looks
> very suspicious, given that you were looking at transaction 25. I
> mean, I'm assuming that your tree is only a couple of revisions
> old...so there's no way you could have a node in it that was created
> in revision 25. Bogosity.
In case this helps identify the problem. I have a working copy like:
$ svn st -u working_copies/log_tests/
A 0 working_copies/log_tests/A/C/epsilon
M 3 working_copies/log_tests/iota
Head revision: 3
When I run 'svn ci working_copies/log_tests' under gdb I see the
following
Breakpoint 3, svn_fs__dag_get_revision (rev=0xbffff5c0, node=0x807ba30,
trail=0x8079618) at subversion/libsvn_fs/dag.c:291
291 SVN_ERR (get_node_revision (&node_rev, node, trail));
(gdb) n
292 *rev = atoi ((SVN_FS__NR_HDR_REV (SVN_FS__NR_HEADER (node_rev)))->data);
(gdb) p node_rev[0].children[0].children[0].next[0]
$5 = {is_atom = 1, data = 0x807bb88 "216:03:2\001", len = 1, children = 0x0,
next = 0x0}
and the revison number comes out at 216. That might be memory
corruption, but could it be that the correct revison is 2, and that
there is a missing null terminator? The len field indcates 1 but
atoi() won't use that.
Using svnadmin I see the transaction
Txn 18:
Created: Mon 17 Dec 2001 16:05:20.808207 (day 351, dst 0, gmt_off 000000)
Author: pm
Log (0 bytes):
==========================================
A/ <1.3>
mu <19.1> [22]
B/ <2.2>
lambda <7.1> [26]
E/ <3.2>
alpha <5.2> [26]
beta <4.1> [24]
F/ <6.1>
C/ <8.2>
epsilon D/ <9.2>
gamma <18.1> [25]
G/ <10.2>
rho <12.2> [24]
pi <11.2> [23]
tau <13.1> [23]
H/ <14.2>
chi <15.1> [23]
omega <17.2> [26]
psi <16.1> [23]
iota <20.2> [25]
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006