Hi,
Pedro Côrte-Real:
> > The owfs header looks something around this.
>
> It can't really be that because it only happens when reading uncached
> and the code does one 24 byte read for the header and then another for
> the payload with the size given in the header.
I've never seen this. Things to do:
* check that you're actually using the offset+payload_length fields
instead of blindly using the whole data portion of the message ;-)
* verify with "strace -s200" that you really do receive that header
as part of the payload, instead of running into a bug in your code,
* post (a link to) the strace output to the list if you still can't find
the problem.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
The most difficult light bulb to replace burns out first and most
frequently.
-- Joe Anderson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
