public inbox for [email protected]  
help / color / mirror / Atom feed
From: Tomas Vondra <[email protected]>
To: Andres Freund <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Nathan Bossart <[email protected]>
Subject: Re: strange valgrind reports about wrapper_handler on 64-bit arm
Date: Sat, 8 Mar 2025 23:48:22 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<i73pjuqcqgv5lsprc76z4bug55okadxpzpuijnup34qmqtwexi@gakdkcyjox5l>
	<[email protected]>

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


Attachments:

  [text/x-log] valgrind.log (1.5K, ../[email protected]/2-valgrind.log)
  download | inline:
==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;"

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: strange valgrind reports about wrapper_handler on 64-bit arm
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox