>>> Ok. Could we perhaps work together to fix it?
>>> I'm thinking something along the lines of:
>>> - you adding 5 debug print's inside the method that's called when a
>>> pipe read occurs
>
> That's not that easy. It's not just a simple function which is called
> there but many nested function calls.
Skip the nested functions, just insert them in the first invoked function.
I'm happy to see just how far it gets, I don't care about the specifics.
We can always narrow it down once we've found ca. which function dies.
>>> - you compile and slap the binary in my general direction (ftp or
nightly dir)
>>> - i'll test and report back how far it got?
>>
>> Alternative:
>> I've got VS.Net installed, so another solution could be that I
>> download whatever sources are needed and start hacking on it myself.
>
> I think that would be best!
Ok. I was probably gonna end up doing that in the long run.
Do notice that this is gonna take time (months?) before I put out
something productive.
If you want a working cache in time for a 1.2.0 release (or perhaps
even 1.1.4?), we're gonna have to do it in cooperation mode.. I can
actually reproduce at will, it takes less than 5 minutes to do a debug
run. I imagine slapping a few printf("I'm this far now")'s in the
code and compiling takes about the same time, so we *could* probably
nuke this bug in a matter of a few hours back-and-forth.
Sorry if I'm pushy. It's just that I've put extra effort into testing
tsvn bugs lately, seeing as multiple releases are forthcoming in a
very soonish manner :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Mar 27 13:21:16 2005