-
Notifications
You must be signed in to change notification settings - Fork 107
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
Issue in hexdecode_string() #167
Comments
This seems to work in 3_6.beta currently. |
@chassell Ok, I am looking to code and there is no change in any code. Sic :-) |
Phooey!! I have a big big change set up for 3_6.beta. What's the Fedora problem? Try again if you need to. The build has been shifting a lot. |
@chassell heh.. I understand, that you are doing changes. :-) Thanks for it. Ad Fedora) We have amanda 3.5.1 and build is failing for long time. Failing on this test. See issue: https://bugzilla.redhat.com/show_bug.cgi?id=2045195 . |
I reviewed this patch and it's working. |
From https://bugzilla.redhat.com/show_bug.cgi?id=2045195
There is failing test:
Error output is this:
Same error in debian build log: http://qa-logs.debian.net/2022/03/26/amanda_3.5.1-8_unstable.log
Exact error is in common-src/hexencode-test.c on line 78
From Petr Písař:
That's an exception from glib2 and glib2-devel was upgraded from 2.70.2-4.fc36 to 2.71.0-1.fc36. So the failure can be triggered by glib2.
However, there is also a bug in the testing function:
hexdecode_string() is documented to return NULL in case of an error. The test "%" is expected to fail, hence it should return NULL. If it does, then a condition (!tmp) in the testing function will falsely report a test failure.
But the most importat bug is in hexdecode_string():
In case of "%", strlen("%") sets new_len=1. (str[0] == '%') is true, new_len underflows to (size_t)-1.
The text was updated successfully, but these errors were encountered: