Open
Conversation
Owner
|
Where is it being called with a NULL format string? I'm more worried about the call site. |
Author
|
It actually happens at build time of nlopt with gcc-asan, prior to using its functions in nloptr. Three other warnings seem to be raised as well: see full details in 00install.out.txt. |
Contributor
|
When sanitizers are enabled with GCC, many "middle-end" warnings are unreliable and known to produce false positives (e.g. 1 2). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gcc-ubsanandgcc-asanshowoccurring in
stop.cspecifically in functionnlopt_vsprintf().According to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116834, the fix is to first check that the pointer to
formatis not null and abort if it is before callingvsnprintf().