Skip to content
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

tests: fix test_monitor on musl #222

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Conversation

alyssais
Copy link
Contributor

It is probably a Glibc bug that sscanf as used by bluez accepts 0x01 for this value. For portability, use the unprefixed hex value. Based on bluez's own documentation, I don't think the 0x is required.

It is probably a Glibc bug that sscanf as used by bluez accepts 0x01
for this value[1].  For portability, use the unprefixed hex value.
Based on bluez's own documentation, I don't think the 0x is
required[2].

[1]: https://www.openwall.com/lists/libc-coord/2024/10/15/2
[2]: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/client/bluetoothctl-monitor.rst?id=3d9900eb754d277ef6abf21bed827cdc9e79ddb4
Copy link
Owner

@martinpitt martinpitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ugh, starting the day with reading the (thankfully long past) exclamations from Ulrich Drepper.. But aside from this, thanks for that insight into the sscanf() mess.

Thank you!

@martinpitt martinpitt merged commit 1a8d872 into martinpitt:main Oct 16, 2024
17 of 18 checks passed
@alyssais alyssais deleted the test_monitor branch October 16, 2024 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants