>> I'm getting a crash during conversion when GetPathDepth recurses
>> itself forever (Perl exhausts its address space then segfaults). It
>> appears to be caused by a pair of physicalaction rows which refer to
>> each other
>
> Thanks Richard, although I wasn't able to test the patch since I
> n
Richard Hughes wrote:
This is a resurrection of a thread from 6 months ago, for which I now
have more information. The basic background was:
I'm getting a crash during conversion when GetPathDepth recurses
itself forever (Perl exhausts its address space then segfaults). It
appears to be caus
This is a resurrection of a thread from 6 months ago, for which I now
have more information. The basic background was:
>> I'm getting a crash during conversion when GetPathDepth recurses
>> itself forever (Perl exhausts its address space then segfaults). It
>> appears to be caused by a pair of phy
> thanks for the report. The problem is, that there is already a fix in
> the code, to protect against multiple move merges. Do you get any
> warning like: Multiple child recs for parent MOVE rec 70374?
No, the only non-status messages are:
Using a hash as a reference is deprecated at Vss2Svn/Du
Hi, Richard,
thanks for the report. The problem is, that there is already a fix in
the code, to protect against multiple move merges. Do you get any
warning like: Multiple child recs for parent MOVE rec 70374?
The solution in r323 is not 100% perfect, since it will only test the
first matche