Parsing fails when endianness of the system that generated and read the stdf are different #1
Description
What steps will reproduce the problem?
1. Read a datalog generated by a big-endian system with a little-endian system
or vice-versa.
What is the expected output? What do you see instead?
It should work, but the parser will fail at offset 0x208 of the stdf
What version of the product are you using? On what operating system?
0.0.2, Windows 7 and RedHat Linux 5 update 6.
Please provide any additional information below.
The root cause is that the length of the FAR record is read as 512 (0x0200)
instead of 2 (0x0002) when the endianness is mismatched. So the parser skips to
0x204 to read the next record and fails. When the endianness is changed the
length needs to be set to 0x0002 to ensure that the parser to records the next
record correctly.
Original issue reported on code.google.com by dkar...@gmail.com on 17 Nov 2013 at 6:52