Nope. We just had to find the source of the crashes, we use the AFSClient on
WinXP SP2 Machines with a really instable program (3d modeller for ancient
buildings). So the software we use is really specific and buggy, really hard to
find the problems in this combination.
So there came the new 1.3.73 just before we found the problems and til now it
looks like our problems are solved (nevertheless, the bugggy software still
crahes, but no more the afsclient).
OpenAFS for Windows should not crash no matter how buggy your other software is. If you are receiving crashes, especially if they are
regularly reproducible I want to see the stack traces. This is why
we ship installers which contain "debugging symbols".
If users of the software do not report the problems they encounter, how am I supposed to fix them?
Jeffrey Altman
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
