On 3/8/25 21:38, Tomas Vondra wrote:
>
> I've restarted check-world with valgrind on my rpi5 machines, with
> current master. I can try running other stuff once that finishes in a
> couple hours.
>
Shortly after restarting this I got three more reports - all of them are
related to strcoll_l. This is on c472a18296e4, i.e. with the asserts
added in this thread etc. But none of those seem to fail.
regards
--
Tomas Vondra
==189168== Conditional jump or move depends on uninitialised value(s)
==189168== at 0xA683CC: wrapper_handler (pqsignal.c:90)
==189168== by 0x580BB9E7: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==189168== Uninitialised value was created by a stack allocation
==189168== at 0x4F94660: strcoll_l (strcoll_l.c:258)
==189168==
{
<insert_a_suppression_name_here>
Memcheck:Cond
fun:wrapper_handler
obj:/usr/libexec/valgrind/memcheck-arm64-linux
}
==189168== Conditional jump or move depends on uninitialised value(s)
==189168== at 0xA683F0: wrapper_handler (pqsignal.c:91)
==189168== by 0x580BB9E7: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==189168== Uninitialised value was created by a stack allocation
==189168== at 0x4F94660: strcoll_l (strcoll_l.c:258)
==189168==
{
<insert_a_suppression_name_here>
Memcheck:Cond
fun:wrapper_handler
obj:/usr/libexec/valgrind/memcheck-arm64-linux
}
==189168== Use of uninitialised value of size 8
==189168== at 0xA684D4: wrapper_handler (pqsignal.c:110)
==189168== by 0x580BB9E7: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==189168== Uninitialised value was created by a stack allocation
==189168== at 0x4F94660: strcoll_l (strcoll_l.c:258)
==189168==
{
<insert_a_suppression_name_here>
Memcheck:Value8
fun:wrapper_handler
obj:/usr/libexec/valgrind/memcheck-arm64-linux
}
**189168** Valgrind detected 3 error(s) during execution of "ANALYZE functional_dependencies;"
