Hi Paul,
Sure I will! With owfs from CVS today, owserver running in background and
owfs running in gdb a TAB after the last ll...typeK
[EMAIL PROTECTED] owfs]$ ll /mnt/1-wire/
total 0
drwxr-xr-x 1 root root 1 May 18 20:15 01.C0DE550A0000
drwxr-xr-x 1 root root 1 May 18 20:15 10.321DC6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.3F55C6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.4957C6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.9324C6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.D381C6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.D83AC6000800
drwxr-xr-x 1 root root 1 May 18 20:15 10.E52BC6000800
drwxr-xr-x 1 root root 1 May 18 20:15 30.2D7709110000
drwxr-xr-x 1 root root 1 May 18 20:11 alarm
drwxr-xr-x 1 root root 1 May 18 20:11 bus.0
drwxr-xr-x 1 root root 1 May 18 20:11 settings
drwxr-xr-x 1 root root 1 May 18 20:15 simultaneous
drwxr-xr-x 1 root root 1 May 18 20:11 statistics
drwxr-xr-x 1 root root 1 May 18 20:11 structure
drwxr-xr-x 1 root root 1 May 18 20:11 system
drwxr-xr-x 1 root root 1 May 18 20:11 uncached
[EMAIL PROTECTED] owfs]$ ll /mnt/1-wire/30.2D7709110000/type
type typeB/ typeE/ typeJ/ typeK/ typeN/ typeR/ typeS/ typeT/
[EMAIL PROTECTED] owfs]$ ll /mnt/1-wire/30.2D7709110000/typeK
gives a seg fault:
==========================================================
CALL: FSTAT path=/30.2D7709110000/typeN
CALL: PARSENAME path=[/30.2D7709110000/typeN]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: ATTRIBUTES path=/30.2D7709110000/typeN
NODEID: 8
unique: 128, error: 0 (Success), outsize: 136
unique: 129, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 129, error: 0 (Success), outsize: 112
unique: 130, opcode: LOOKUP (1), nodeid: 2, insize: 46
LOOKUP /30.2D7709110000/typeR
CALL: FSTAT path=/30.2D7709110000/typeR
CALL: PARSENAME path=[/30.2D7709110000/typeR]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: ATTRIBUTES path=/30.2D7709110000/typeR
NODEID: 9
unique: 130, error: 0 (Success), outsize: 136
unique: 131, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 131, error: 0 (Success), outsize: 112
unique: 132, opcode: LOOKUP (1), nodeid: 2, insize: 46
LOOKUP /30.2D7709110000/typeS
CALL: FSTAT path=/30.2D7709110000/typeS
CALL: PARSENAME path=[/30.2D7709110000/typeS]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: ATTRIBUTES path=/30.2D7709110000/typeS
NODEID: 10
unique: 132, error: 0 (Success), outsize: 136
unique: 133, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 133, error: 0 (Success), outsize: 112
unique: 134, opcode: LOOKUP (1), nodeid: 2, insize: 46
LOOKUP /30.2D7709110000/typeT
CALL: FSTAT path=/30.2D7709110000/typeT
CALL: PARSENAME path=[/30.2D7709110000/typeT]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: ATTRIBUTES path=/30.2D7709110000/typeT
NODEID: 11
unique: 134, error: 0 (Success), outsize: 136
unique: 135, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 135, error: 0 (Success), outsize: 112
unique: 136, opcode: LOOKUP (1), nodeid: 1, insize: 56
LOOKUP /30.2D7709110000
CALL: FSTAT path=/30.2D7709110000
CALL: PARSENAME path=[/30.2D7709110000]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: ATTRIBUTES path=/30.2D7709110000
NODEID: 2
unique: 136, error: 0 (Success), outsize: 136
unique: 137, opcode: OPENDIR (27), nodeid: 2, insize: 48
unique: 137, error: 0 (Success), outsize: 32
unique: 138, opcode: READDIR (28), nodeid: 2, insize: 64
CALL: GETDIR path=/30.2D7709110000
CALL: PARSENAME path=[/30.2D7709110000]
DEBUG: Get from cache sn 30 2D 77 09 11 00 00 A6 in=(nil) index=-1 size=0
DEBUG: Found in cache
CALL: DIRECTORY path=/30.2D7709110000
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208420032 (LWP 11148)]
0x00573668 in FS_devdir (dirfunc=0xbff9f924, pn2=0xbff9f83c) at ow_dir.c:272
272 dirfunc( pn2 ) ;
================================================================
After 3 or 4 ll /mnt/1-wire a seg fault i another line took place:
==================================================================
CALL: FSTAT path=/simultaneous
CALL: PARSENAME path=[/simultaneous]
CALL: ATTRIBUTES path=/simultaneous
NODEID: 18
unique: 72, error: 0 (Success), outsize: 136
unique: 73, opcode: READDIR (28), nodeid: 1, insize: 64
unique: 73, error: 0 (Success), outsize: 16
unique: 74, opcode: RELEASEDIR (29), nodeid: 1, insize: 56
unique: 74, error: 0 (Success), outsize: 16
unique: 75, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 75, error: 0 (Success), outsize: 112
unique: 76, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 76, error: 0 (Success), outsize: 112
unique: 77, opcode: OPENDIR (27), nodeid: 1, insize: 48
unique: 77, error: 0 (Success), outsize: 32
unique: 78, opcode: GETATTR (3), nodeid: 1, insize: 40
CALL: FSTAT path=/
CALL: PARSENAME path=[/]
CALL: ATTRIBUTES path=/
unique: 78, error: 0 (Success), outsize: 112
unique: 79, opcode: READDIR (28), nodeid: 1, insize: 64
CALL: GETDIR path=/
CALL: PARSENAME path=[/]
CALL: DIRECTORY path=/
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208420032 (LWP 11376)]
0x00450182 in FS_dir_both (dirfunc=0xbfa9ff44, pn=0xbfa9fefc,
flags=0xbfa9fec4, local_flag=1) at ow_dir.c:102
102 dirfunc( &pn2 ) ;
(gdb)
=============================================================
But I can't see the pattern in the seg faults; sometimes it seg faults
after the first ll sometimes after 3 or 4 and when run in gdb even after
maybe 10 ll's
Jan B.
On Tue, May 16, 2006 19:40, Paul Alfille wrote:
> I take that back. We weren't rechecking.
>
> Can you run with --foreground --error_level=9 and see where it stops?
> That will give some hints.
>
> Paul
>
> On 5/16/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
>> Hi Jan,
>>
>> 2.3p6 at least seems stable when not using owserver (see Christian's
>> note -- I'm working on it).
>>
>> I do notice that we are (unnecessarily) rechecking the presence of a
>> device as it gets displayed for a directory listing. This could start
>> a new thread on the stack, and certainly is inefficient. The next
>> release will change it. Try p7 when it's released (I hope today).
>>
>> Paul
>>
>>
>> On 5/16/06, Jan Bertelsen <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > After some days with beautiful spring weather here in Denmark, I'm
>> back at
>> > the keyboard happy to find that owhttpd and owserver (owfs-2.3p5) is
>> > running without any problem on my Fedora Core 5. Nice work!
>> >
>> > owfs is still getting some seg faults but not all the time. When I
>> read a
>> > specific value like a temperature it's working as supposed, but
>> anything
>> > involving directories (like file completion) can make owfs to seg
>> fault.
>> >
>> > After a seg fault I unmount /mnt/1-wire with fusermount -u and restart
>> > owfs. Then owfs will serve one or two ll /mnt/1-wire
>> >
>> > As far I can see there is still embedded functions in owhttpd/owserver
>> so
>> > I don't think that's the problem...
>> >
>> > Best regards
>> >
>> > Jan B.
>> >
>> >
>> > -------------------------------------------------------
>> > Using Tomcat but need to do more? Need to support web services,
>> security?
>> > Get stuff done quickly with pre-integrated technology to make your job
>> easier
>> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> > http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
>> > _______________________________________________
>> > Owfs-developers mailing list
>> > Owfs-developers@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>> >
>>
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
