[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: crash when fetching status

From: Folker Schamel <schamel23_at_spinor.com>
Date: 2004-11-05 18:54:57 CET

kfogel@collab.net wrote:
> Folker Schamel <schamel23@spinor.com> writes:
>>I don't see how fixing the crash itself as suggested by Steve or Julian
>>does have bad consequences for the long term.
>>You still can - and have to! - find the real underlaying bug.
> I understand what you're saying. But masking the underlying bug
> *does* reduce our ability to find the bug, because once it's masked,
> users will encounter it less often, thus reducing our chances of
> getting a reproduction recipe.
> Of course, any developer can undo the mask fix and probe for the real
> bug, but that requires running a modified Subversion all the time.
> This is impractical and unscalable -- what if there are multiple such
> masks to undo? In practice, we depend on the user community for
> reproduction recipes.

I think there is a difference between
a) fixing an ugly crash, and
b) making it easier to find a different bug.

For example, Julian's proposal fixes the crash,
but makes it even easier to to find the other, underlaying bug,
because users get a more well-defined error.

It's no game "short-verm versus long-term" if you can have both.


> In this case, it seems Philip managed to conjure up the bug just by
> thinking ("He fixes radios by thinking!"). But if he hadn't done
> that, the short-term/long-term tradeoff would be a real concern.
> I hope this helps explain it better.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 5 18:55:34 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.