(I do not have an easy way to login to the issue tracker from my iPad...so,
moving back to the list...)
I really do not think the assert is due to memory corruption - nothing I
saw indicated that was happening. I think it is far more likely that there
is another bug somewhere. (It is the simplest explanation, IMHO.)
If the checkout continues beyond the xxx lines in that patch (the xxx lines
indicate when we would have otherwise gone into a bad state and hung later
on) and does not end up in an infinite loop or hang, then I think this
issue can be resolved. And, someone who knows more about libsvn_wc can
investigate the assert. In the meantime, I will clean up the patch
tomorrow and commit it to serf... -- justin
On Wednesday, June 13, 2012, wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3981
>
>
>
>
>
>
> ------- Additional comments from philip_at_tigris.org <javascript:;> Wed Jun
> 13 13:59:29 -0700 2012 -------
> I'm not seeing hangs very often at present so it's hard to know whether the
> patch helps. With the patch applied a checkout of tags asserts:
>
> svn: E235000: In file '../src/subversion/libsvn_wc/wc_db.c' line 1707:
> assertion
> failed (SVN_IS_VALID_REVNUM(changed_rev))
>
> That happens on debian and ubuntu. Before the assert I see lines like:
>
> xxx!!! 0x1001458 0x1cbbd98 0x1cbbe18 0x1001358
> xxx!!! 0x1001458 0x1001358 (nil) (nil)
> xxx!!! 0xa358f8 0x5a5eb58 0x5a5ebd8 0xa357f8
> xxx!!! 0xa358f8 0xa357f8 (nil) (nil)
> xxx!!! 0x5a5ead8 0x54e6018 0x54e6098 0x5a5ebd8
> xxx!!! 0x5a5ead8 0x5a5ebd8 (nil) (nil)
> xxx!!! 0x1cbbd18 0x108fdd8 0x1049a18 0x1cbbe18
> xxx!!! 0x1cbbd18 0x1cbbe18 (nil) (nil)
> xxx!!! 0x5a5dc58 0x5829ab8 0x5829a38 0x5a5dd58
> xxx!!! 0x5a5dc58 0x5a5dd58 (nil) (nil)
> xxx!!! 0x31cec68 0xe9a798 0x33170a8 0x31ced68
>
>
Received on 2012-06-13 23:51:07 CEST