| 
      
      
      From: Vlad C. <Vla...@ma...> - 2006-09-24 01:15:53
       | 
| Hi, I'm trying to get a feel for how Fuse works by debugging the sample "hello.c" program provided on your website. I compiled it and fuse-2.5.3 using the "-g" option, and I'm running the "hello" executable in the Eclipse debugger. Strangely, it seems that some lines of code are being executed over and over again. For example, the debugger goes to line 322, then to line 321, then to line 322, then to line 321, then to line 322 in helper.c before finally going to line 258. Later on, there are other instances where this type of repetition occurs (ie. in helper.c: line 142, then line 138, then line 142, then line 138, then line 142, etc). I recorded a 5-minute screen-capture video showing how the same lines of code are being repeatedly executed: http://www.angelfire.com/ex2/foss/fuse/fuse_debug.html Is this behavior a bug, is it an artifact of debugging, or am I just doing something wrong? Thanks for your help, Vlad | 
| 
      
      
      From: Mattias W. <ma...@su...> - 2006-09-24 10:04:31
       | 
| Try to compile without optimization, -O0 or no -O flag at all. -Mattias Vlad Codrea wrote: > Hi, > > I'm trying to get a feel for how Fuse works by debugging the sample > "hello.c" program provided on your website. I compiled it and fuse-2.5.3 > using the "-g" option, and I'm running the "hello" executable in the > Eclipse debugger. > > Strangely, it seems that some lines of code are being executed over and > over again. For example, the debugger goes to line 322, then to line > 321, then to line 322, then to line 321, then to line 322 in helper.c > before finally going to line 258. Later on, there are other instances > where this type of repetition occurs (ie. in helper.c: line 142, then > line 138, then line 142, then line 138, then line 142, etc). > > I recorded a 5-minute screen-capture video showing how the same lines of > code are being repeatedly executed: > > http://www.angelfire.com/ex2/foss/fuse/fuse_debug.html > > Is this behavior a bug, is it an artifact of debugging, or am I just > doing something wrong? > > Thanks for your help, > Vlad > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > fuse-devel mailing list > fus...@li... > https://lists.sourceforge.net/lists/listinfo/fuse-devel > > | 
| 
      
      
      From: Vlad C. <Vla...@ma...> - 2006-09-24 14:40:01
       | 
| Mattias Wadman wrote: > Try to compile without optimization, -O0 or no -O flag at all. > > I deleted the old fuse-2.5.3 directory and unpacked fuse-2.5.3.tar.gz. After removing the "-O2" from configure.in, and then running ./configure and ./make, I get the following error: libtool: Version mismatch error. This is libtool 1.5a, but the libtool: definition of this AC_PROG_LIBTOOL comes from an older release. libtool: You should recreate aclocal.m4 with macros from libtool 1.5a libtool: and run autoconf again. Someone else has previously reported this error (http://sourceforge.net/mailarchive/forum.php?thread_id=9109011&forum_id=42692), and the proposed solution was to run a script called 'makeconf.sh' or to run 'autoreconf'. 'makeconf.sh' doesn't seem to exist, and running 'autoreconf' doesn't get rid of the error. I'd like to point out that if I don't modify configure.in, everything compiles. Any ideas? Thanks, Vlad | 
| 
      
      
      From: Mattias W. <ma...@su...> - 2006-09-24 15:21:02
       | 
| Vlad Codrea wrote: > Mattias Wadman wrote: >> Try to compile without optimization, -O0 or no -O flag at all. >> >> > > I deleted the old fuse-2.5.3 directory and unpacked fuse-2.5.3.tar.gz. > After removing the "-O2" from configure.in, and then running ./configure > and ./make, I get the following error: > > libtool: Version mismatch error. This is libtool 1.5a, but the > libtool: definition of this AC_PROG_LIBTOOL comes from an older release. > libtool: You should recreate aclocal.m4 with macros from libtool 1.5a > libtool: and run autoconf again. If you edit configure.in and run make the Makefile will try to regenerate the configure script by running autoconf, you probably need "good" and compatible versions of autoconf, automake and libtool to make it work, it's usualy quite messy :) > Someone else has previously reported this error > (http://sourceforge.net/mailarchive/forum.php?thread_id=9109011&forum_id=42692), > and the proposed solution was to run a script called 'makeconf.sh' or to > run 'autoreconf'. 'makeconf.sh' doesn't seem to exist, and running > 'autoreconf' doesn't get rid of the error. If you checkout fuse from CVS there is a makeconf.sh script, it's not included when doing a .tar.gz distribution. But usualy it just runs autoconf and does some other things, so you will probably get the same error. > I'd like to point out that if I don't modify configure.in, everything > compiles. > > Any ideas? Yes, run ./configure CFLAGS="-Wall -W -g -O0" -Mattias | 
| 
      
      
      From: Vlad C. <Vla...@ma...> - 2006-09-24 15:41:08
       | 
| Mattias Wadman wrote: > Vlad Codrea wrote: >> Mattias Wadman wrote: >>> Try to compile without optimization, -O0 or no -O flag at all. >>> >>> >> >> I deleted the old fuse-2.5.3 directory and unpacked >> fuse-2.5.3.tar.gz. After removing the "-O2" from configure.in, and >> then running ./configure and ./make, I get the following error: >> >> libtool: Version mismatch error. This is libtool 1.5a, but the >> libtool: definition of this AC_PROG_LIBTOOL comes from an older release. >> libtool: You should recreate aclocal.m4 with macros from libtool 1.5a >> libtool: and run autoconf again. > > If you edit configure.in and run make the Makefile will try to > regenerate the configure script by running autoconf, you probably need > "good" and compatible versions of autoconf, automake and libtool to > make it work, it's usualy quite messy :) > >> Someone else has previously reported this error >> (http://sourceforge.net/mailarchive/forum.php?thread_id=9109011&forum_id=42692), >> and the proposed solution was to run a script called 'makeconf.sh' or >> to run 'autoreconf'. 'makeconf.sh' doesn't seem to exist, and >> running 'autoreconf' doesn't get rid of the error. > > If you checkout fuse from CVS there is a makeconf.sh script, it's not > included when doing a .tar.gz distribution. But usualy it just runs > autoconf and does some other things, so you will probably get the same > error. > >> I'd like to point out that if I don't modify configure.in, everything >> compiles. >> >> Any ideas? > > Yes, run ./configure CFLAGS="-Wall -W -g -O0" > Fuse compiles now, and using "-O0" solved the debugging problem. Thank you very much for your help! Vlad |