I have a couple of suggestions, that might help: 1. Did you apply both the MacFUSE sshfs patch and the MacFUSE fuse patch to the appropriate sources before compile/install?
2. The error you see is almost certainly from the fuselib that is built as part of the MacFUSE core and linked with your application. I believe it comes from the file 'helper.c' line 111 or thereabouts. The trick is that you have almost no parameters (just the host and the mountpoint), but sshfs has added a few additional ones to the list (see the bottom of the file sshfs.c where fuse_opt_insert_arg appears.) I suspect one of these is not being understood by fuselib (was it patched?) Command line arguments take a long path before they are finally packed up and fed to the kernel. They begin on the line you type in the terminal. Then the file system module typically removes some that were specific to it and adds others that will be interpreted later. These are passed to the fuse_main library entry point which validates them (where you have a problem) and repacks them for submission to mount_fusefs. mount_fusefs validates them once again and packs them into a binary form that is passed to the kernel to configure the new file system. As indicated above, it sounds like one of the params added by sshfs is not being accepted at the fuse lib level. Fuse lib is a pain to debug as a library, so the easiest thing to do is to include the source files directly in the debug version of your file system component (and do not link against the library). Then set a break point at the location where the offending message is issued to see what it is bitching about. If you are new to debugging command line tools under XCode, you can set the arguments passed to the tool in the Arguments tab of the info window of the executables item with the name of the tool (not the products or targets version that may exist). Then debug and the parameters will be passed to the tool and you can trace every little screw-up. You will probably want to add either a -f or a -d flag to prevent the fork that occurs from leaving you with nothing to debug (both prevent the fork from occurring, -d adds debugging noise). Again, I suspect that the problem is the lack of one of the two patches. Good luck. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
