http://rpg.hamsterrepublic.com/bugzilla/show_bug.cgi?id=830
Mike Caron <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Mike Caron <[email protected]> 2010-04-05 21:40:06 PDT --- Preliminary debugging suggests that this is not a bug in *reading* the slice collection, but instead a bug in writing it. Specifically, the string size for the text slice is at position 0x294 (1-based, unless noted otherwise). The value stored there is b10110000. This byte, in VLI terms, is 6-bits meaning the value 0x30 (48), which is the correct string size. However, for some reason, the high bit is also set, which tells the VLI reader to read another byte, and process it. The second byte is b00000001, which is the value 1 (with no more bytes). so, 0x30 << 6 + 1 == 0xC01 == 3073. This is consistent with what I see it reading. (NOTE: This is not actually how much data is read! It only reads up to the end of the file, which is 640 bytes later. That's why it errors claiming to have read 640 bytes!) The question is, where did this extra VLI data come from? That, I am still investigating. Could be a shifting error in WriteVLI. I'll let you know. -- Configure bugmail: http://rpg.hamsterrepublic.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
