the problem is the procedures starting at lines 146 and 148 in svn head,
getb and getw. theyre not checking for eof-object, which would cause this
behaviour. fetch isnt checking either, but it needs to be at getb level,
cause char->integer against eof-object isnt so good. the weird question is
why is this not failing at the char->integer ?
-elf
On Wed, 13 Aug 2008, Joshua Griffith wrote:
The following lines demonstrate the problem:
(use s11n)
(deserialize (open-input-string "\f"))
-Josh
On Aug 13, 2008, at 4:30 AM, felix winkelmann wrote:
On Wed, Aug 13, 2008 at 8:38 AM, Joshua Griffith
<[EMAIL PROTECTED]> wrote:
Hello,
When a serialized object gets corrupted or truncated (which often occurs
when it is transmitted over a TCP connection), attempting to deserialize
that object results in a "Bus error" and immediate program termination,
rather than a raised exception. How difficult would it be to modify the
s11n egg so that it fails gracefully upon receipt of corrupted data?
It shouldn't be too hard, one just would have to precede a chunk of
data with a checksum. I can look into this (unless you need a quick
solution, because I can't exactly say when I get around doing so).
cheers,
felix
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
