#1539 vtkwriter produces unreadable "binary" files on 64 bit
Metadata
Property | Value |
---|---|
Reported by | Jö Fahlke (jorrit@jorrit.de) |
Reported at | Dec 3, 2014 16:11 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Linux 64bit |
Last edited by | Jö Fahlke (jorrit@jorrit.de) |
Last edited at | Mar 13, 2015 21:29 |
Closed by | Jö Fahlke (jorrit@jorrit.de) |
Closed at | Mar 13, 2015 21:29 |
Closed in version | Unknown |
Resolution | Fixed |
Comment |
Description
Nagaiah Chamakuri discovered that the vtkwriter produces vtu files that are unreadable in paraview under certain circumstances:
- 64bit system
- binary format (more precisely: inline base64 format)
- paraview version 398 (or 3.98 or something like that).
Test case: visualization.cc from grid-howto produces vertexdata.vtu which exhibits the problem.
What apparently happens is the following: the inline base64 format encodes the data first as a length and then as the values. The length is piped into the Base64Stream as a long unsigned, which produces 8 bytes to encode on 64 bit machines. However, paraview apparently expects the size to be only 32 bits.
TODO:
- Verify the problem still exists on master.
- Write unit test.
- Fix.