Just fixed the error in the DS2482_channel_select logic. Can you retry from
the CVS?
Thanks, Paul
On Wed, Feb 11, 2009 at 11:21 AM, Jan Kandziora <j...@gmx.de> wrote:
> Am Mittwoch, 11. Februar 2009 schrieb Paul Alfille:
> > I looked at the log -- nothing remarkable. A memory leak of 36 bytes was
> > nice to find.
> >
> > Can you test the newer version and see if the problem persists?
> >
> With latest CVS from CET 17:00 I get:
>
> % OW::get uncached
>
> 29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,bus.7/,bus.6/,bus.5/,bus.4/,bus.3/,bus.2/,bus.1/,bus.0/,settings/,system/,statistics/,structure/,alarm/
>
> The chip is surely only on bus.0, I'm using a DS2482-800. The "alarm" bug
> seems to have gone "a little". I can list "alarm"
>
> % OW::get alarm
>
> 29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,29.E53401000000/,uncached/
> % OW::put 29.E53401000000/por 0
> % OW::get alarm
> uncached/
> % OW::get alarm/uncached
> Segmentation fault
>
> Uh oh. And OW::finish still segfaults. Result snipped now:
>
> DEBUG: ParsedName_destroy uncached/structure
> CALL: PARSENAME path=[uncached/alarm]
> DEBUG: ParsedName_destroy uncached/alarm
> DEBUG: FS_dir_both out ret=0
> DEBUG: FS_OWQ_destroy of uncached
> DEBUG: ParsedName_destroy uncached
> CALL: Clear Cache
> CALL: Closing input devices
> *** glibc detected *** /usr/bin/tclsh: double free or corruption (fasttop):
> 0x09066a60 ***
> ======= Backtrace: =========
> /lib/libc.so.6[0xb7e72fc4]
> /lib/libc.so.6(cfree+0x9c)[0xb7e7495c]
> /opt/owfs/lib/libow-2.7.so.14(FreeIn+0x8c)[0xb7d35b2c]
> /opt/owfs/lib/libow-2.7.so.14(FreeInAll+0x34)[0xb7d35e84]
> /opt/owfs/lib/libow-2.7.so.14(LibStop+0x72)[0xb7d44f92]
> /opt/owfs/lib/libow-2.7.so.14(API_finish+0x3f)[0xb7d30e2f]
> /opt/owfs/lib/libowcapi-2.7.so.14(OW_finish+0x17)[0xb7dc41e7]
> /usr/lib/tcl/owtcl-0.2/ow.so(Owtcl_Delete+0x26)[0xb80836b6]
> /usr/lib/libtcl8.5.so[0xb7f9c25b]
> /usr/lib/libtcl8.5.so[0xb7f9ce4f]
> /usr/lib/libtcl8.5.so(Tcl_EvalEx+0x2e)[0xb7f9d6fe]
> /usr/lib/libtcl8.5.so(Tcl_FSEvalFileEx+0x14f)[0xb800db5f]
> /usr/lib/libtcl8.5.so(Tcl_Main+0x392)[0xb8016962]
> /usr/bin/tclsh(main+0x39)[0x8048759]
> /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e1d5f5]
> /usr/bin/tclsh[0x8048621]
>
> Kind regards
>
> Jan
> --
> Vor Onboard-Grafik sollte man mit Aufklebern wie auf Zigarettenschachteln
> warnen...
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code
> to
> build responsive, highly engaging applications that combine the power of
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK
> and
> Ajax docs to start building applications today-
> http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
