From: Greenwade, R. S <rsgreenwade@DIRECTV.com> - 2005-02-28 23:20:32
|
Hello .. I'm considering using Fuse for a work project and have created a demonstration of it based upon fusexmp. My application seems to run fine single-threaded, but not multi-threaded. The only system calls that were added to fusexmp.c other than file access functions and string functions are random & srandom, however I don't even hit them before I run into my problem. The program exits after helper.c:fuser_setup_common()=3D>daemon() .. = which is expected, but I can't get GDB to follow the child, the child's PID doesn't show up with the 'ps' command, and all references to /dev/fuse return with the following message: Transport endpoint is not connected It appears that when daemon(0, 1) is called, both the parent and the child just exits. Any suggestions for how to debug this problem? Rob Greenwade rob...@sb... |
From: Valient G. <vg...@po...> - 2005-02-28 23:52:42
|
Try running in foreground mode ('-f' switch if your example is passing through flags to fuse). The default background mode doesn't allow you to see any print statements coming from libfuse. If you're using a recent release of libfuse, the fuse_main routine returns an error code, so you might also check for that in your program to see if libfuse returned an error.. regards, Valient Greenwade, Robert S wrote: >Hello .. > >I'm considering using Fuse for a work project and have created a >demonstration of it based upon fusexmp. My application seems to run >fine single-threaded, but not multi-threaded. The only system calls >that were added to fusexmp.c other than file access functions and string >functions are random & srandom, however I don't even hit them before I >run into my problem. > >The program exits after helper.c:fuser_setup_common()=>daemon() .. which >is expected, but I can't get GDB to follow the child, the child's PID >doesn't show up with the 'ps' command, and all references to /dev/fuse >return with the following message: Transport endpoint is not connected > >It appears that when daemon(0, 1) is called, both the parent and the >child just exits. Any suggestions for how to debug this problem? > > >Rob Greenwade >rob...@sb... > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_ide95&alloc_id396&op=click >_______________________________________________ >fuse-devel mailing list >fus...@li... >https://lists.sourceforge.net/lists/listinfo/fuse-devel > > |