Philip Martin wrote:
> SteveKing <steveking@gmx.ch> writes:
>> I just received another crashreport, but this time the user actually
>> could provide additional information:
> Just had another thought: I wonder if this problem occurs when a
> Subversion thread/process is actively modifying the working copy while
> another thread/process runs status? Getting information from the
> users who experience the problem would help, but you said earlier that
> you gets lots of reports and yet we still don't know what the working
> copy looks like when it occurs. Should we give up attempting to
> understand the problem and apply the "fix"?
Can't we get any more information out of this one user who has been
(much) more helpful? Like a tarball of the WC?
The problem with the "fix" is that we are still not sure if the rogue
pointer is null or just pointing somewhere illegal.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 23 11:13:10 2004