Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P PolyORB-HI-C
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TASTETASTE
  • PolyORB-HI-C
  • Issues
  • #15
Closed
Open
Issue created Aug 30, 2017 by Javier Herrero Martín@jherreroDeveloper

Port Id endianess when using ACN coding

Hello,

We are communicating a RASTA Board with a Linux VM in a Windows platform in the OSRANET activity. We have found that the Port Id added to the messages used by sporadic interfaces has no endianess treatment. The linux executable crashed due to polyorb code was accessing one of their tables with a very big value.

I had to add a check in the function '__po_hi_get_entity_from_global_port' implemented in 'po_hi_transport.c' and modify the endianess of that field in our driver.

Regards Javier

Assignee
Assign to
Time tracking