-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C binding storage sizes do not match for multiple OS's and architectures #1218
Labels
bug
Something isn't working
Comments
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
This was referenced Mar 3, 2022
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
… to the C binding using the heap
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 3, 2022
elBoberido
added a commit
that referenced
this issue
Mar 3, 2022
…-constructs Iox #1218 use heap for c binding constructs
elBoberido
added a commit
to ApexAI/iceoryx
that referenced
this issue
Mar 4, 2022
…in binding C tests
21 tasks
elBoberido
added a commit
that referenced
this issue
Mar 4, 2022
…usage-of-storage-in-binding-c-tests iox-#1218 Remove potential dangerous usage of storage in binding C tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
The C binding uses arrays with magic numbers to provide a storage for C++ constructs. This is more brittle than expected and breaks on multiple platforms and architectures.
In order to fix this, the heap should be used until there is a proper solution for the magic number problems. This might be solved by #308
The text was updated successfully, but these errors were encountered: