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

MVE: Don't hardcode vsnprintf() destination buffer size #576

Conversation

andre-schulz
Copy link
Collaborator

This MR contains a minor improvement to a vsnprintf() call which was introduced in a recent commit.

@andre-schulz andre-schulz changed the title MVE: Make vsnprinf() usage more robust MVE: Make vsnprintf() usage more robust Sep 2, 2024
@andre-schulz andre-schulz force-pushed the make_vsnprintf_usage_more_robust branch from a0e4e27 to 3990d4f Compare September 2, 2024 21:21
@andre-schulz andre-schulz marked this pull request as ready for review September 2, 2024 21:34
@andre-schulz andre-schulz force-pushed the make_vsnprintf_usage_more_robust branch from 3990d4f to 05cc0cd Compare September 2, 2024 23:03
@andre-schulz andre-schulz changed the title MVE: Make vsnprintf() usage more robust MVE: Don't hardcode vsnprintf() destination buffer size Sep 2, 2024
Use sizeof() instead of hardcoding destination buffer size when calling
vsnprintf().

Fixes: 247ea30 ("MVE: Replace vsprintf() with vsnprintf()")
@andre-schulz andre-schulz force-pushed the make_vsnprintf_usage_more_robust branch from 05cc0cd to a4bb65f Compare September 2, 2024 23:14
@simonfuhrmann simonfuhrmann merged commit b48d14f into simonfuhrmann:master Sep 3, 2024
9 checks passed
@andre-schulz andre-schulz deleted the make_vsnprintf_usage_more_robust branch September 4, 2024 19:40
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