scanner: no longer dump debug messages to stderr #57
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.
When varlink_object_new_from_json is fuzzed it receives a lot of bogus json strings and clutters stderr with messages like "2 != 4" instead of just returning errors. Given that it's the only place where fprintf is used like that it seems it was left there accidentally and can probably be safely removed to make the API more consistent in general.
It should make it easier to fuzz the library and other than that it should also make it possible to compile libvarlink on some architectures without compiler warnings like