Hi Matt, When working on a MacFUSE file-system I experienced this and a number of other problems - edge cases of various kinds - places where the Finder threw it's hands up in horror etc. For me the most valuable tool in my tool-kit was the Loopback file system. If you can get the loopback to show a problem then you probably have a problem in MacFUSE (I never could) otherwise there is some difference between the Loopback and your own file system that is the problem. After struggling with some thorny problems I managed to mod our code so that I could run the loopback code in parallel to our own and compare results between the two (in the debugger) to pin down problems - I mention this as it could be that you could do the same. Certainly the loopback is a really good place to start debugging.
Best regards Alan _________________________________________________________________ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCB&publ=WLHMTAG&crea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
