Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 740
    • Issues 740
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 198
    • Merge requests 198
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #12819
Closed
Open
Created Dec 20, 2011 by Kitware Robot@kwrobotOwner

Wrong byte order for long (64bit) in vtkDataReader/vtkDataWriter

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


When a vtkLongArray is written with the vtkDataWriter on a system where sizeof(long) = 8 the byte order is changed within a block of 8 bytes [0 1 2 3 4 5 6 7] -> [7 6 5 4 3 2 1 0]. But when the data is read back with vtkDataReader it uses a block size of 4 for swapping the byte order for long. This results when writing and reading (as in marshalling/unmarshalling in vtkCommunicator) in an ordering of [4 5 6 7 0 1 2 3]. I do not know if the behaviour of the reader or writer is correct and if an exchange between systems with 32bit and 64bit is even possible. The attached file is an example that should reproduce the explained bug on 64bit systems.

Assignee
Assign to
Time tracking