Ok, found this bug. Basically the device directory request and visibility tests weren't being sent to the server, but being performed in owhttpd. since the BAE0910 wasn't connected to owhttpd except via owserver, it caused a problem.
This will be part of OWFS 2.8p5 when it's released. Thanks for the report and the easy test case. Paul Alfille On Tue, Nov 9, 2010 at 2:16 PM, Jan Bertelsen <jb-o...@w57.dk> wrote: > Hi Pascal, > > very interesting - with owhttpd or owfs connected directly to the busmaster I > can access the BAE 910 chip and all its registers and even change the content > of a user register (at least via owhttpd) - without any crash. > > Further when I access a property with the "cat" command and with owfs > connected to owserver I can also read and write a register - and no crash. But > as soon I use any "dir" functions they crash > > So it seems to be a problem with the "dir" function when owhttpd and owfs are > running as clients. > > Regards, > > Jan > > > > On Sun, November 7, 2010 08:25, Pascal Baerten wrote: >> Hi Jan, >> >> Could you do the test with owfs directly connected on the busmaster (without >> owserver) and post the trace? >> >> also it will be interesting to try accessing a explicit property without ls. >> >> like this: >> cat /mnt/1wire/FC.000000000022/910/pioc >> regards >> >> Pascal >> >> 2010/11/6 Jan Bertelsen <jb-o...@w57.dk> >> >>> Hi, >>> >>> thanks for the answer - unfortunately I still have the same problem. I have >>> tried both the code from CVS and the versions 2.7p39, 2.8p1 and 2.8p3 all >>> with >>> the same result. owhttpd and owfs are crashing (see my first post below) >>> when >>> I try to access the BAE 910 chip. >>> >>> I'm not running the normal kernel on my server as Ubuntu server edition is >>> compiled with PAE and my CPU does not have this addressing feature - can >>> this >>> be the cause?? >>> >>> As I'm not a skilled C-debugger so any help is mostly welcome. >>> >>> Best regards, >>> >>> Jan >>> >>> On Mon, November 1, 2010 08:42, Pascal Baerten wrote: >>> > Hi Jan, >>> > >>> > I got similar issues with intermediate owfs version that introduced >>> > visibility feature. >>> > The visibility feature allows to conditionally hide non relevant >>> properties. >>> > This allows to show adaptive directory structure between bae0910 and >>> bae0911 >>> > who share same family code. >>> > >>> > This issue is fixed in the current cvs version. >>> > You may consider to revert to previous release or to test with cvs >>> version. >>> > >>> > Pascal >>> > >>> > >>> > >>> > >>> > 2010/10/31 Jan Bertelsen <jb-o...@w57.dk> >>> > >>> >> Hi all, >>> >> >>> >> trying to read registers on the BAE 910 chip I get a segmentation fault >>> in >>> >> owhttpd (see below) and owfs. I have no problem reading other devices on >>> >> the >>> >> bus. >>> >> >>> >> When I try to read the BAE chip using owfs: >>> >> >>> >> ls /mnt/1wire/FC.000000000022/910 >>> >> >>> >> it's the same, owfs is crashing with the same debug information. >>> >> >>> >> owhttpd and owfs are connected to the 1wire bus via owserver, which is >>> >> running >>> >> as: >>> >> >>> >> owserver -p 2125 -d /dev/ttyS0 >>> >> >>> >> owserver is not affected of the crash. >>> >> >>> >> My setup is: >>> >> System: Ubuntu 8.04.4 LTS Hardy >>> >> OWFS: compiled from owfs-2.8p2.tar.gz >>> >> Bus master: LinkOEM (same as Link45) at /dev/ttyS0 >>> >> >>> >> >>> >> Any hints are welcome as I'm not used to debug c programs. >>> >> >>> >> Best regards >>> >> >>> >> Jan >>> >> >>> >> ================================================ >>> >> >>> >> $ gdb owhttpd >>> >> run -s 2125 -p 2121 --debug >>> >> <..cut..> >>> >> DEBUG: owhttpd_handler.c:handle_GET(151) Simple GET request -- read a >>> >> value >>> >> or directory >>> >> DEBUG: ow_dir.c:FS_dir(63) path=/FC.000000000022/910 >>> >> CALL: ow_dir.c:FS_dir_both(98) path=/FC.000000000022/910 >>> >> DEBUG: ow_cache.c:Cache_Get_Internal(884) FC 00 00 00 00 00 22 DE >>> size=4 >>> >> DEBUG: ow_parseobject.c:OWQ_create_from_path(29) /FC.000000000022/910 >>> >> CALL: ow_parsename.c:FS_ParsedName_anywhere(90) >>> >> path=[/FC.000000000022/910] >>> >> DEBUG: ow_cache.c:Cache_Get_Device(855) FC 00 00 00 00 00 22 DE >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1067) Get from cache sn FC 00 00 00 >>> 00 >>> >> 00 >>> >> 22 DE pointer=0xb7efc920 index=0 size=4 >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1076) value found in cache. >>> Remaining >>> >> life: 117 seconds. >>> >> DEBUG: ow_presence.c:CheckPresence(75) Found device on bus 0 >>> >> DEBUG: ow_parseobject.c:OWQ_create_sibling(62) Create sibling >>> device_type >>> >> from /FC.000000000022/910 as /FC.000000000022/device_type >>> >> DEBUG: ow_parseobject.c:OWQ_create_from_path(29) >>> >> /FC.000000000022/device_type >>> >> CALL: ow_parsename.c:FS_ParsedName_anywhere(90) >>> >> path=[/FC.000000000022/device_type] >>> >> DEBUG: ow_cache.c:Cache_Get_Device(855) FC 00 00 00 00 00 22 DE >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1067) Get from cache sn FC 00 00 00 >>> 00 >>> >> 00 >>> >> 22 DE pointer=0xb7efc920 index=0 size=4 >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1076) value found in cache. >>> Remaining >>> >> life: 117 seconds. >>> >> DEBUG: ow_presence.c:CheckPresence(75) Found device on bus 0 >>> >> DEBUG: ow_read.c:adjust_file_size(333) file_length=12 offset=0 size=1 >>> >> DEBUG: ow_parseobject.c:OWQ_create_sibling(62) Create sibling typestate >>> >> from >>> >> /FC.000000000022/device_type as /FC.000000000022/typestate >>> >> DEBUG: ow_parseobject.c:OWQ_create_from_path(29) >>> >> /FC.000000000022/typestate >>> >> CALL: ow_parsename.c:FS_ParsedName_anywhere(90) >>> >> path=[/FC.000000000022/typestate] >>> >> DEBUG: ow_cache.c:Cache_Get_Device(855) FC 00 00 00 00 00 22 DE >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1067) Get from cache sn FC 00 00 00 >>> 00 >>> >> 00 >>> >> 22 DE pointer=0xb7efc920 index=0 size=4 >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1076) value found in cache. >>> Remaining >>> >> life: 117 seconds. >>> >> DEBUG: ow_presence.c:CheckPresence(75) Found device on bus 0 >>> >> DEBUG: ow_read.c:adjust_file_size(333) file_length=12 offset=0 size=1 >>> >> DEBUG: ow_cache.c:Cache_Get(783) FC 00 00 00 00 00 22 DE size=8 >>> >> IsUncachedDir=0 >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1067) Get from cache sn FC 00 00 00 >>> 00 >>> >> 00 >>> >> 22 DE pointer=0xb7ef8a58 index=0 size=8 >>> >> DEBUG: ow_cache.c:Cache_Get_Common(1095) value not found in cache >>> >> DEBUG: ow_select.c:BUS_select(72) Selecting a path (and device) >>> >> path=/FC.000000000022/typestate SN=FC 00 00 00 00 00 22 DE last path=FF >>> 00 >>> >> 00 00 00 00 00 00 >>> >> DEBUG: ow_select.c:BUS_select(77) Clearing root branch >>> >> >>> >> Program received signal SIGSEGV, Segmentation fault. >>> >> [Switching to Thread 0xb7cbfb90 (LWP 19258)] >>> >> 0x00000000 in ?? () >>> >> (gdb) >>> >> >>> >> >>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >>> >> Nokia and AT&T present the 2010 Calling All Innovators-North America >>> >> contest >>> >> Create new apps & games for the Nokia N8 for consumers in U.S. and >>> Canada >>> >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >>> >> marketing >>> >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >>> >> http://p.sf.net/sfu/nokia-dev2dev >>> >> _______________________________________________ >>> >> Owfs-developers mailing list >>> >> Owfs-developers@lists.sourceforge.net >>> >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >>> >> >>> > >>> > >>> > >>> > -- >>> > Pascal >>> > www.brain4home.eu >>> > to subscribe, send a mail to <list-subscr...@brain4home.eu> >>> > >>> ------------------------------------------------------------------------------ >>> > Nokia and AT&T present the 2010 Calling All Innovators-North America >>> contest >>> > Create new apps & games for the Nokia N8 for consumers in U.S. and >>> Canada >>> > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >>> marketing >>> > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >>> > >>> http://p.sf.net/sfu/nokia-dev2dev_______________________________________________ >>> > Owfs-developers mailing list >>> > Owfs-developers@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/owfs-developers >>> > >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >>> David G. Thomson, author of the best-selling book "Blueprint to a >>> Billion" shares his insights and actions to help propel your >>> business during the next growth cycle. Listen Now! >>> http://p.sf.net/sfu/SAP-dev2dev >>> _______________________________________________ >>> Owfs-developers mailing list >>> Owfs-developers@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >>> >> >> >> >> -- >> Pascal >> www.brain4home.eu >> to subscribe, send a mail to <list-subscr...@brain4home.eu> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
