Bug #88135 | Use of uninitialised value of size 8 at (item_timefunc.cc:398) | ||
---|---|---|---|
Submitted: | 18 Oct 2017 7:10 | Modified: | 19 Oct 2017 0:58 |
Reporter: | yghmgl yang | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.37 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | debug valgrind-build |
[18 Oct 2017 7:10]
yghmgl yang
[18 Oct 2017 13:53]
MySQL Verification Team
Hi! Thank you for your report. I must say that this looks to me rather like a bug in the valgrind. If we take a peak in the code, we can see that everything is fine: ******************************************************************************************** /* Conversion specifiers that match classes of characters */ case '.': while (my_ispunct(cs, *val) && val != val_end) val++; break; case '@': while (my_isalpha(cs, *val) && val != val_end) val++; break; case '#': while (my_isdigit(cs, *val) && val != val_end) /* offending line */ val++; break; default: goto err; ******************************************************************************************** First of all, my_isdigit() is a macro that does not introduce any variables of its own. Second, CHARSET pointer `cs` is initialized at the very start of the same function, while the character pointer `val` is fully initialized in the calling function, which is val_datetime(). That is first proof. Now to the second one ... If you look at the code in all other `case`s, you will notice that those all use the same variables in the very similar and even identical fashion. And there are no errors for those cases ???? This makes this error a bug in valgrind.
[18 Oct 2017 13:55]
MySQL Verification Team
One last note. We use Valgrind regularly for all our builds and we can differentiate with valid reports from the invalid ones.
[18 Oct 2017 16:25]
MySQL Verification Team
This bug is a duplicate of the internal bug, that is fixed in 5.7. It will not be fixed in 5.6 as it does not pop-up there in the testsuite.
[19 Oct 2017 0:58]
yghmgl yang
This bug is a duplicate of the internal bug, that is fixed in 5.7. It will not be fixed in 5.6 as it does not pop-up there in the testsuite. >>> HI,Sinisa thanks for your analysis, can you tell me the bug # that is fixed in 5.7.
[19 Oct 2017 11:19]
MySQL Verification Team
Hi! As I wrote, this is an internal bugs , accessible only by Oracle employees and customers. Are you sure that you have access to it ??