Actually no... Since owhttpd doesn't work for you, the problem is
probably not located in fuse (or wrong installed fuse)
/Christian
On Tue, 2005-09-13 at 14:54 -0400, Phil Strong wrote:
> OK so I heard recently that fuse is in the new kernel standard now.
> Do you think upgrading to that new ke
OK so I heard recently that fuse is in the new kernel standard
now. Do you think upgrading to that new kernel could rule out any
issues I may or may not be having with fuse so we can concentrate on
OWFS?On 9/13/05, Christian Magnusson <[EMAIL PROTECTED]> wrote:
I'm not sure why it crash, and I dou
I'm not sure why it crash, and I doubt I could fix it without really
logging in to your server and find out by myself.
The backtrace from owhttpd you sent, is either missing debug-information
or perhaps the stack got corrupted.
As far as I know you are running Fedora Core 3 which should have a
w
(gdb) run --foreground --error_level=9 -u -p
Starting program: /opt/owfs/bin/owhttpd --foreground --error_level=9 -u -p
[Thread debugging using libthread_db enabled]
[New Thread -1208424768 (LWP 10116)]
INFO: PARSENAME path=
ERR: Opened USB DS9490 adapter at 002/002.
: No data available
Ok when I run it as root I get this
(gdb) run --foreground --error_level=9 -u /mnt/1wire/
Starting program: /opt/owfs/bin/owfs --foreground --error_level=9 -u /mnt/1wire/
[Thread debugging using libthread_db enabled]
[New Thread -1208596800 (LWP 10069)]
Detaching after fork from child process 1007
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209006400 (LWP 5508)]
0x005f676a in FS_dir (dirfunc=0xbfe68e90, pn=0xbfe68ec0) at ow_dir.c:108
108
dirfunc( &pn2 ) ;
(gdb) bt
#0 0x005f676a in FS_dir (dirfunc=0xbfe68e90, pn=0xbfe68ec0) at ow_di
(gdb) run --foreground --error_level=9 -u /mnt/1wire/
Starting program: /opt/owfs/bin/owfs --foreground --error_level=9 -u /mnt/1wire/
[Thread debugging using libthread_db enabled]
[New Thread -1208842560 (LWP 5372)]
Detaching after fork from child process 5373.
INFO: PARSENAME path=
ERR: Failed t
I guess you have to debug this with gdb. Could you try to turn
on the core dumps in your shell:
tcsh: limit coredumpsize unlimited
bash: ulimit -c unlimited
Start owfs and do you crashing ls.
> /opt/owfs/bin/owfs --error_level=9 -u /mnt/1wire/
> ls /mnt/1wire/
Check if any core-file is generate
Ok with new unit and after I reinstalled both fuse (tested) and owfs (newest cvs) I get the following
[EMAIL PROTECTED] /]# /opt/owfs/bin/owfs --error_level=9 -u /mnt/1wire/
INFO: PARSENAME path=
ERR: Opened USB DS9490 adapter at 002/002.
: No data available
INFO: DS9490_setup_adapter: done
INFO
Awesome I will try it when I get home Paul thanks so far for all your help.On 8/30/05, Alfille, Paul H.,M.D. <
[EMAIL PROTECTED]> wrote:Hmm... I think both would work well, as well as the DS9490 (USB) and the LINK
adapters.Before you do that, try something I'm uploading now: OWFS-DSLI mentioned it
Hmm... I think both would work well, as well as the DS9490 (USB) and the LINK
adapters.
Before you do that, try something I'm uploading now: OWFS-DSL
I mentioned it in another post, but now the unified CD image is available.
It is a bootable live-CD distribution with owfs already configured.
Do
11 matches
Mail list logo
