- Notifications
You must be signed in to change notification settings - Fork81
CanFdSocket
read_frame crash fix#61
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
pd0wm commentedMar 13, 2024
Does |
I think so. Fixed it too |
Oof. Sorry, my bad. I was hacking on this update before I got an FD controller. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
Update socketcan-rs to v3.3.1 which solve the issue regarding the CANFD messages:-socketcan-rs/socketcan-rs#61Signed-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
Update socketcan-rs to v3.3.1 which solve the issue regarding the CANFD messages:-socketcan-rs/socketcan-rs#61Signed-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
Changes:- Update socketcan-rs to v3.3.1 which solve the issue regarding the CANFD messages: -socketcan-rs/socketcan-rs#61- Update Cargo.lock files under main and staging workspaceSigned-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
Changes:- Update socketcan-rs to v3.3.1 which solve the issue regarding the CANFD messages: -socketcan-rs/socketcan-rs#61- Update Cargo.lock files under main and staging workspaceSigned-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
Reading a standard CAN frame through the
CanFdSocket
leads to a crash due to mismatching sizes in the frame construction’scopy_from_slice
. Thix fix has been tested and builds valid CAN frames.