Skip to content

Fix creation of invalid Unicast Bindings - #8288

Merged
manup merged 1 commit into
dresden-elektronik:masterfrom
manup:master
Aug 1, 2025
Merged

Fix creation of invalid Unicast Bindings#8288
manup merged 1 commit into
dresden-elektronik:masterfrom
manup:master

Conversation

@manup

@manup manup commented Aug 1, 2025

Copy link
Copy Markdown
Member

Seen on macOS somehow clang did not init all fields of the binding to zero when creating an object via DDF_Binding result = {}. The u64 dstExtAddress wasn't initialized only the u16 dstGroup in the union. The ext address was some random stuff from memory.

The fix ensures all fields including dstExtAdress are zero. And the unicast destination address is filled with the actual coordinator mac address.

Note: Invalid bindings from previous releases are automatically cleaned up and repaired by the Device state machine.

Seen on macOS somehow clang did not init all fields of the binding to zero when creation an object via `DDF_Binding result = {}`.
The u64 dstExtAddress wasn't initialized only the u16 dstGroup in the union. The ext address was some random stuff from memory.

The fix ensures all fields and dstExtAdress are zero. And the unicast dst address is filled with the actual coordinator mac address.
@manup manup added this to the v2.31.0-beta milestone Aug 1, 2025
@manup manup added the Fix label Aug 1, 2025
@manup
manup merged commit eed786c into dresden-elektronik:master Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant