Package: tdom
Version: 0.9.5-1.1
Tags: ftbfs
Usertags: hppa powerpc
Testcase fails like this:
---- Result was:
1 {error "not well-formed (invalid token)" at line 14048575688 character
50379238646}
---- Result should have been (exact matching):
1 {error "not well-formed (invalid token)" at line 3 character 11}
==== attrList-4.1 FAILED
The interesting part here is that 14048575688 is hex value 0x3.455C40C8
and 50379238646 is hex value 0xB.BAD62CF6.
In both cases the "upper" 32bits (0x3, and 0xb=11 decimal) have the expected
value.
hppa and powerpc are 32-bit platforms, and both big endian.
The problem is somewhere in the code, where a 32-bit "(unsigned?)long" value is
written to
memory, but somewhere else a 64-bit "long" value is read back.
Please make sure to use e.g. "uint64_t" type instead to avoid such problem.
Helge
