Valgrind warning for uninitialised bytes in sum_distinct test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
We are seeing a valgrind warning about uninitialised bytes in test sum_distinct.
This appears to have started with revision# 1663:
https:/
CURRENT_TEST: main.sum_distinct
==5383== Thread 16:
==5383== Syscall param write(buf) points to uninitialised byte(s)
==5383== at 0x4372C0B: ??? (in /lib/tls/
==5383== by 0x82C2EB9: drizzled:
==5383== by 0x82C32FD: drizzled:
==5383== by 0x8153F97: drizzled:
==5383== by 0x8156C50: drizzled:
==5383== by 0x8261438: drizzled:
==5383== by 0x81D200C: drizzled:
...
Changed in drizzle: | |
status: | New → Confirmed |