You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user on VTOW discovered that implementing his own cobs_encode function caused his program to crash at runtime, with the stack trace showing only the address 0x3805820.
I believe the issue is that our implementation of cobs_encode in src/common/cobs.c is a public symbol, so when the hot and cold packages link at runtime, the links their cobs_encode calls to our implementation. The main thing is that the symbols for our implementation should be stripped.
This should be investigated further to see if cobs_encode_measure also causes this issue, and if any other functions in the kernel cause this issue.
The text was updated successfully, but these errors were encountered:
WillXuCodes
changed the title
PROS 3.7.2: cobs_encode() name clashing at runtime
cobs_encode() name clashing at runtime
Jan 12, 2023
A user on VTOW discovered that implementing his own
cobs_encode
function caused his program to crash at runtime, with the stack trace showing only the address 0x3805820.I believe the issue is that our implementation of
cobs_encode
in src/common/cobs.c is a public symbol, so when the hot and cold packages link at runtime, the links theircobs_encode
calls to our implementation. The main thing is that the symbols for our implementation should be stripped.This should be investigated further to see if
cobs_encode_measure
also causes this issue, and if any other functions in the kernel cause this issue.The text was updated successfully, but these errors were encountered: