Re: [Valgrind-users] configure: error: build/install requires that 'sed' is GNU sed

Quoting Edward King zhan...@neusoft.com: My OS is Solaris 10,I install valgrind-3.4.1,like follows: $./configure checking for gdb... /no/gdb/was/found/at/configure/time ehecking for GNU sed... sed:illegal option --version note: GNU sed is only required at build/install time configure:

Re: [Valgrind-users] suppression files with valgrind 3.5.0

attention. Does this mean that building Valgrind on one OS, installing it on an NFS mount and using it from later OSes isn't really supported? A+ Paul -- Paul Floyd http://paulf.free.fr -- Let Crystal

Re: [Valgrind-users] merge valgrind results

Osman, Ahmed wrote: Hi All, Is there a way to merge all runs of valgrind for the same executable in one file? I use cat. A+ Paul -- Paul Floyd http://paulf.free.fr -- Come build with us

Re: [Valgrind-users] valgrind newbie

robert...@aol.com wrote: I am trying to track down a memory leak in my fcgi process. I have used a bit valgrind before but the scenario was a bit less complex. In the current scenario, the fcgi process is started by a lighttpd script using the following command. daemon $FCGI_DAEMON -f

[Valgrind-users] Errors in strncasecmp

Hi We just switched our reference platform to RHEL 6.2, using Valgrind 3.7.0 Now we're getting loads of errors in __GI___strncasecmp_l I see that in memcheck/mc_replace_strmem.c line 680 of 1585 [head svn version] there is STRCASECMP_L(VG_Z_LIBC_SONAME, strcasecmp_l)

Re: [Valgrind-users] Memcheck fails to find error

On 11 Apr 2013, at 21:20, Milian Wolff wrote: Hey there, a friend of mine is starting C++ and asked me this apparently simple question: Why does the following program not show me an error? Hi memcheck is a heap checker, not a stack checker. Try --tool=exp-sgcheck (where sg is stack

Re: [Valgrind-users] there is no callgrind.out

On 18 Apr 2013, at 19:15, Mahmood Naderan wrote: Dear all, I want to use kcachegrind and callgrind to profile my program and find the hotspot. The problem is, I use --tool=callgrind but there is no calgrind output file. Here is the detail: My program at the top level uses a tcl script.

Re: [Valgrind-users] Adding suppressions generates significantly more errors

On 2 Jul 2013, at 19:01, Kevin Lee wrote: I had a relatively simple suppression file that generated ~500 errors. I wrote a script to select certain errors for suppression and generate an additional suppression file. When I run with this additional suppression file, my errors explode to

Re: [Valgrind-users] -m32

Shiva wrote: > Hi Tom, > I am trying to run valgrind on my executable which is of 32-bit. I am > getting the following error: > valgrind > valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit) > valgrind: : cannot execute binary file > > Couple of other logs which are useful: > >

Re: [Valgrind-users] Valgrind hangs when generating supression for Qt5 menus

On 14 Jul 2017, at 21:10, Nathan Bahr wrote: > Hi, > > I made a simple Qt5 application with a single menu item and valgrind is > configured to print suppression code. > > If I open and close a menu, valgrind holds onto the QMenu object and prompts > to print supression code. This causes the

Re: [Valgrind-users] rodata warning

> On 11 Feb 2018, at 21:36, John Reiser wrote: > >> --18142-- WARNING: Serious error when reading debug info >> --18142-- When reading debug info from >> /export/home/paulf/tools/gcc/lib/libstdc++.so.6.0.25: >> --18142-- Can't make sense of .rodata section mapping >>

Re: [Valgrind-users] rodata warning

    Hi John   My first attempt to post the output failed as it was too long.   Here it is on a paste site   https://zerobin.net/?0bf6ea80afca0924#PT/yP+KTPOXYx/+IKUC+wwhm/UCF+S2fccpHQB9Cf7Q=     Here's an extract:   ELF Header:   Magic:   7f 45 4c 46 01 01 01 06 01 00 00 00 00 00 00 00    Class:   

[Valgrind-users] rodata warning

Hi I’m getting this warning: --18142-- WARNING: Serious error when reading debug info --18142-- When reading debug info from /export/home/paulf/tools/gcc/lib/libstdc++.so.6.0.25: --18142-- Can't make sense of .rodata section mapping (GCC SVN head, Solaris 11.3, Valgrind git head). Is it

Re: [Valgrind-users] rodata warning

> On 11 Feb 2018, at 21:36, John Reiser wrote: > >> --18142-- WARNING: Serious error when reading debug info >> --18142-- When reading debug info from >> /export/home/paulf/tools/gcc/lib/libstdc++.so.6.0.25: >> --18142-- Can't make sense of .rodata section mapping >>

Re: [Valgrind-users] rodata warning

> On 13 Feb 2018, at 01:03, John Reiser wrote: > >> https://zerobin.net/?0bf6ea80afca0924#PT/yP+KTPOXYx/+IKUC+wwhm/UCF+S2fccpHQB9Cf7Q= > > [That "paste" site says that the page expires in 6 days.] It’s the first time I’ve used such a site. I don’t know if there are

[Valgrind-users] Massif xtree

Hi I’ve been using Massif recently and I gave the xtree output a go (using the callgrind format output). Am I right in saying that, by default, the stats given are for the entire run? This means that the total allocs/frees give a good idea of the memory churn for the run. However, the

Re: [Valgrind-users] Valgrind Solaris port - current and future shape

> On 18 Jun 2018, at 15:39, Ivo Raisr wrote: > > Dear Valgrind'ers, > > I have been maintaining the Valgrind Solaris (and partly also illumos) > port for nearly three years, > ensuring it builds and runs on the latest Solaris 11.1, 11.2, 11.3 > (and 11.4 until April 2018). > > > I am still

Re: [Valgrind-users] [Valgrind-developers] valgrind-3.14.0.RC2 is available for testing

> On 6 Oct 2018, at 01:05, Roger Light wrote: > > Hello, > > I built and tested on a Mac with OS X version 10.13.6. I have the same > problem with the tarball, but the git checkout built just fine. > > make regtest produced: > > == 643 tests, 328 stderr failures, 83 stdout failures, 1

Re: [Valgrind-users] HELP/Hint: valgrind error message

  > Message du 15/05/20 10:22 > De : "Kunal Chauhan" > ==6660== Warning: Can't execute setuid/setgid/setcap executable: ./lte_tr069 > ==6660== Possible workaround: remove --trace-children=yes, if in effect > ==6660== > valgrind: ./lte_tr069: Permission denied Hi The problem is that your

Re: [Valgrind-users] compat_ioctl cmd does not match even if it shows same value

> This is incorrect for C99 and indeed any compiler that supports "long long". > On such systems, the integer constant 3222829167 > has type "long long", and it is absolutely guaranteed to preserve that value > when cast to unsigned. Assuming 32-bit int, of course. It is also incorrect for

Re: [Valgrind-users] DHAT speed

 > That doesn't sound right. I use DHAT extensively and expect a slowdown of> perhaps 50:1, maybe less. What you're describing is a slowdown factor of> at least several thousand.>> Bear in mind though that (1) V sequentialises thread execution, which wil> make a big difference if the program is

Re: [Valgrind-users] DHAT speed

[snip - perf] Well, no real surprises. This is with a testcase that runs standalone in about 5 seconds and under DHAT in about 200 seconds (so a reasonable slowdown of 40x). # Overhead Command Shared Object

[Valgrind-users] DHAT speed

Hi   I'm running DHAT on what I consider to be a relatively small example. Standalone the executable runs in a bit under 10 minutes. Based on the CPU time that we print after every 10% of progress, under DHAT the same executable is going to take about 422 hours - about two and a half weeks.  

Re: [Valgrind-users] DHAT speed

On 5/26/20, Paul FLOYD wrote: > > I'm running DHAT on what I consider to be a relatively small example. > > Standalone the executable runs in a bit under 10 minutes. Based on the CPU > > time that we print after every 10% of progress, under DHAT the same executable is going

Re: [Valgrind-users] DHAT speed

> Message du 26/05/20 13:19> De : "John Reiser" the ratio is about 1:50. So > right away, that's a hardware slowdown of 4X.Maybe more. The machine has > 12Mbyte of cache according to cpuinfo.> Valgrind runs every tool > single-threaded. So if your app averages 5 active threads,> then that is a

Re: [Valgrind-users] Generation of report

De : "Shemin Aboobacker" > > if we are using automated gui testing tool with valgrind and automated > testing tool kills > the application after GUI testing ,valgrind gives incomplete report.Is there > any solution for this?  On Linux I suppose? Which signal is being used for the kill?

Re: [Valgrind-users] [Hint]: valgrind outcome concern

> Hi Team, > Q.As for a valgrind usage , is valgrind only checks the memory leakage of > code which hits only? > Q As for a can valgrind checks the all the code of binary without hitting rhe > scenerio. In code? Kunal Broadly speaking, there are two categories of software analysis tools. 1.

Re: [Valgrind-users] Print summary before exec

> De : "François-Xavier Carton via Valgrind-users" > Hi, I have a program that calls exec without forking. I would like to run > that program under valgrind > and get a summary report for the code before the call to exec. > I don't want to trace the exec'ed program, so the --trace-children

Re: [Valgrind-users] MySQL related messages

On 6/7/20 16:11 UTC, James Read wrote: > I found the FAQ https://dev.mysql.com/doc/refman/8.0/en/faqs.html but > couldn't find the answer you were referring to. > Any clues as to which part of the FAQ I should be looking in? I think that John was referring to the Valgrind FAQ

Re: [Valgrind-users] MySQL related messages

Hi If you want to be certain then you will need to run with debug information. There may be something like a "mysql-debuginfo" package that you could install. That said, "still reachable" memory is often harmless, caused by libraries caching information. Similar questions have been asked on

Re: [Valgrind-users] Generation of report

Hi again OK, a few more details. There is nothing that you can do about SIGKILL. Your process gets terminated and you get no chance to do anything about it. Valgrind cannot do it’s final resource leak checks and your log is probably truncated. SIGTERM, on the other hand, gives you a chance

Re: [Valgrind-users] Please give me advises: How to use the snapshot parameter used in VALGRIND's massif in external applications like Python or ROS/ROS2

On 19/01/2021 17:52, Koki Nagahama wrote: Hi VALGRIND developers and users, I'm planning to modify a part of your product, VALGRIND,to integrate it with a middleware for robots called ROS. In order to do this, I'm considering two ways to implement the massif component of VALGRIND: (1) to

Re: [Valgrind-users] [valgrind]: mem leaks

On 1/22/21 9:31 PM, Kunal Chauhan wrote: Hi Team, As on my linux  board ,one of process showing some run time memory increase as seen by pmap command. So how valgrind can be useful to search such mem leaks in big code. Or is there is way to attached valgrind and see where and which

Re: [Valgrind-users] [valgrind]: mem leaks

> On 24 Jan 2021, at 18:29, Kunal Chauhan wrote: > > Hi paul, > > thanks for info, > 1.Like in trailing mail you said process under completion what do you mean > exactly, > 2. Also for running a process under valgrind my binary should be strip or > unstrip.? > > 3. Memcheck tool where

Re: [Valgrind-users] how to attach valgrind to more than one process at a time

> On 1 Jun 2021, at 06:46, gangadhara reddy chavva > wrote: > > Hi, > > I am working on network routers where there will be multiple protocols > running as different processes. if i want to attach the valgrind for more > than one process at the same time what is the command/option to use.

Re: [Valgrind-users] Valgrind musl 1.2.2 bug

On 4/26/21 8:23 PM, Kyryl Melekhin wrote: Hello valgrind community! This is my first message ever to this mailing list. I am currently experiencing a weird bug in valgrind, where it mistakenly does not recognize malloc/free/realloc function and also produces weird warnings. But only on musl

Re: [Valgrind-users] [valgrind]: mem leaks

> On 25 Jan 2021, at 11:49, Kunal Chauhan wrote: > > Thanks for clarifications > ++ if the binary is crashed or may be not crashed when it runs with valgrind, > but in both case valgrind is able to give the report. ? Hi If your application causes a segmentation fault, the OS will send it a

Re: [Valgrind-users] Valgrind-3.17.0.RC1 is available for testing

On 3/15/21 1:33 PM, Mark Wielaard wrote: Greetings. A first release candidate for 3.17.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.17.0.RC1.tar.bz2 (md5 = 9df201b3461a1709993ffc50d0920bd7) Please give it a try on platforms that are important for you. If no serious issues

Re: [Valgrind-users] No "by" message in memcheck output

> De : "Michael Ortiz" > Objet : [Valgrind-users] No "by" message in memcheck output Hi It's possible that the call to malloc is before the start of main (either from your libc or for the initialization of some static or global object). I know next to nothing about the ARM ABI, but on amd64

Re: [Valgrind-users] valgrind-3.18.0.RC1 is available for testing

On 10/12/21 10:13 PM, Mark Wielaard wrote: An RC1 tarball for 3.18.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.18.0.RC1.tar.bz2 (md5sum = 6babaf9e145055a2c9b50cbd2ddfefc0) (sha1sum = ccc73895097cba83cf7664b02edc66866e98a31b) Please give it a try in configurations that

Re: [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit

On 20/10/2021 20:13, Paul Floyd wrote: On 10/20/21 16:16, Paul FLOYD wrote: Message du 20/10/21 17:14 De : "Vladislav Yaglamunov" A : valgrind-users@lists.sourceforge.net Copie à : Objet : [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit I am usin

Re: [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit

On 10/20/21 16:16, Paul FLOYD wrote: Message du 20/10/21 17:14 De : "Vladislav Yaglamunov" A : valgrind-users@lists.sourceforge.net Copie à : Objet : [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit I am using Valgrind 3.17.0 and noticed a strange behavior whi

Re: [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit

On 21/10/2021 20:45, Florian Weimer wrote: * Paul Floyd: Unless someone else has an Idea this is going to need some debugging inside Valgrind. It's probably the glibc implementation that is incorrectly executed by valgrind. “g++ -fno-builtin” reproduces the issue with the original sources

Re: [Valgrind-users] Cubic root of zero gives wrong result with clang 64-bit

> Message du 20/10/21 17:14 > De : "Vladislav Yaglamunov" > A : valgrind-users@lists.sourceforge.net > Copie à : > Objet : [Valgrind-users] Cubic root of zero gives wrong result with clang > 64-bit > >Hi, >I am using Valgrind 3.17.0 and noticed a strange behavior while running a code

Re: [Valgrind-users] 'make check' for valgrind-3.18.1

On 18/12/2021 21:07, John Crow wrote: Fwiw I'm seeing a failure, snippet below, when running `make check` on valgrind-3.18.1. The package configures, makes, installs, and, as far as I can tell, executes successfully. $ uname -a Linux foo-Inspiron-3583 5.4.0-91-generic #102-Ubuntu SMP Fri Nov

Re: [Valgrind-users] 'make check' for valgrind-3.18.1

Hi John On 12/19/21 16:16, John Crow wrote: I ought to have said at first how much I appreciate having Valgrind available. It's invaluable, and thank you for your attention. 'You are building with the same compiler that was used at configure time?' Yes. I verified by doing a

Re: [Valgrind-users] Using Valgrind with custom memory management

  > Could you please suggest if Valgrind has provisions to help detect memory > leaks, for applications such as ours. Hi Abhijit Yes, Valgrind has provisions for this. It will, however, require you to modify your code. The procedure is documented in the manual here

Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC2 is available for testing

> On 27 Oct 2023, at 00:54, Mark Wielaard wrote: > > Thanks. > > = I ran make regtest on Fedora 38 POWER9 ppc64le and got: > > == 732 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > memcheck/tests/bug340392 (stderr)

Re: [Valgrind-users] Suspect "uninitialised value(s)" error

On 11/10/2023 23:47, Karl Robillard via Valgrind-users wrote: I'm getting the following error on struct members which should absolutely be initialized: Conditional jump or move depends on uninitialised value(s) To begin investigating I did a memset of zero on the entire struct and the error

Re: [Valgrind-users] Suspect "uninitialised value(s)" error

On 12/10/2023 10:06, Tom Hughes wrote: That's not any part of the problem code though, so it's not really relevant to the original problem. There's no way we can comment on the original problem though because we can't actually see any of the code, only a few top level highlights which is

Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing

On 10/20/22 01:52, Mark Wielaard wrote: Greetings. A first release candidate for 3.20.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.20.0.RC1.tar.bz2 (md5 = 981b9276536843090700c1268549186e) Please give it a try on platforms that are important for you. If no serious

Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing

On 10/20/22 01:52, Mark Wielaard wrote: Greetings. A first release candidate for 3.20.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.20.0.RC1.tar.bz2 (md5 = 981b9276536843090700c1268549186e) Please give it a try on platforms that are important for you. If no serious

Re: [Valgrind-users] compiling Valgrind 3.19.0 on Solaris 11

Can you try https://github.com/oracle/solaris-userland/tree/master/components/valgrind One day I’ll get round to contacting the Oracle support team that produced this with a view to merging it upstream. A+ Paul ___ Valgrind-users mailing list

Re: [Valgrind-users] tond...@yahoo.co.uk compiling Valgrind 3.19.0 on Solaris 11

On 8 Sept 2022 15:27, Shane Bishop wrote: Hi, I am trying to compile Valgrind 3.19.0 on Solaris  Is there an earlier release of Valgrind that is known to successfully compile on Solaris 11 that I could try building instead?If you have Oracle support I believe that they have a version

Re: [Valgrind-users] Valgrind trace Memory Addresses while running?

> On 5 Aug 2022, at 20:53, G N Srinivasa Prasanna > wrote: > >  > This is the first time we are using Valgrind, and we want to know if we can > get a list of all the physical addresses the program used, in the order the > program accessed them, and whether read/write. > > Please let us

Re: [Valgrind-users] [SGCheck][Array overrun detection] seems found nothing in multiple version

Hi Sgcheck never got beyond experimental and was removed from Valgrind a few versions ago. My advice is simply to not use it. A+ Paul > On 4 Aug 2022, at 07:45, Pahome Chen via Valgrind-users > wrote: > >  > Dear all, > > I read the sgcheck’s doc and know it’s a experimental tool, but it

Re: [Valgrind-users] memory leak reported many times, but only one instance should be possible

On 16-01-23 22:02, Gordon Messmer wrote: Can anyone suggest why valgrind prints so many loss records for this particular leak?  Links for the two functions that I mentioned follow, along with one of the loss records printed by valgrind. In my experience the most likely reason that you are

Re: [Valgrind-users] Cache conflict detection support in cachegrind

On 29-01-23 14:31, Ivica B wrote: Hi! I am looking for a tool that can detect cache conflicts, but I am not finding any. There are a few that are mostly academic, and thus not maintained. I think it is important for the performance analysis community to have a tool that to some extent can

Re: [Valgrind-users] Timer delete

Yes, the cache disabling is quite hacky, as mentionnd in the doc: "Valgrind disables the cache using some internal knowledge of the glibc stack cache implementation and by examining the debug information of the pthread library. This technique is thus somewhat fragile and might not work

Re: [Valgrind-users] Timer delete

On 11/12/22 01:46, John Reiser wrote: It's a bug (or implementation constraint) in glibc timer. When I run it under valgrind-3.19.0 with glibc-debuginfo and glibc-debugsource installed (2.35-17.fc36.x86_64): [Notice the annotation "LOOK HERE"] ==281161== Command: ./a.out ==281161==

Re: [Valgrind-users] Timer delete

Hi I've done most of the work to get the pthread stack cache turned off with glibc >= 2.34. (see https://bugs.kde.org/show_bug.cgi?id=88). This doesn't help with this example, and it looks to me that this is a problem with libc / rtld. A+ Paul

Re: [Valgrind-users] Timer delete

On 11/11/22 17:47, Domenico Panella wrote: Hi, I am getting a memory leak in my program about timer_delete function. According valgrind output, It seems that the timer_delete function doesn't release the memory. ==18483== HEAP SUMMARY: ==18483== in use at exit: 272 bytes in 1 blocks

Re: [Valgrind-users] Compilation fails on ARM

On 27-02-23 22:11, Leon Pollak wrote: Hello, all. I am trying to compile Valgrind 3.20.0 on ARMv7 Linux 2.6.37 (not cross!). At first, compilation produced a lot of errors with binary constants in the form 0b, but I replaced them with normal numbers and compilation continued. It failed

Re: [Valgrind-users] Need Help

> On 16 Feb 2023, at 00:37, Anand K R wrote: > > 0x66 0xF 0x3A 0x22 > I can’t see what that disassembles to. Can you tell us what CPU exactly this is for, and which OS and compiler you are using? Do you get any call stacks (for Valgtind itself or the test exe)? Lastly, can you provide

Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing

Nothing bad to report. I'll do one more test on Solaris 11.3 tomorrow. FreeBSD 13.1 amd64 No change FreeBSD 13.2 amd64 I get a hang in drd/tests/pth_cancel_locked and a few more fails, most likely related to switching from clang 13 to 14. FreedBSD 13.2 x86 As for amd64 but also a new

Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing

On 22-04-23 23:41, Paul Floyd wrote: OpenIndiana 22.10 Everything builds. All the gdbserver tests hang. And I should have said the hangs aren't new. A+ Paul ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https

Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing

On 04/22/23 11:41 PM, Paul Floyd wrote: Nothing bad to report. I'll do one more test on Solaris 11.3 tomorrow. Solaris 11.3 amd64 No python3, and I only have python3.4 (and no 'python3' metapackage either) on my machine that is long out of service contract. So I got some moans about

Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing

On 23-04-23 13:58, Paul Floyd wrote: Still to come: Alpine/musl. It configures. It all builds. It's not great. == 619 tests, 102 stderr failures, 27 stdout failures, 1 stderrB failure, 2 stdoutB failures, 4 post failures == But that's good enough for me :-) A+ Paul

Re: [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill)

On 29-03-23 04:41, John Reiser wrote:  Could it be possible to add an option like --heap-up-fill --heap-down-fill (like for stack with malloc), that fills heap memory with a specified values (when entering a function and leave a function)? tl;dr 2 See

Re: [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill)

On 28-03-23 11:40, Julien Allali wrote: Hi, Sometimes, valgrind detects error like "Conditional jump or move depends" or "Use of uninitialized value" related to a variable in heap. When using with gdb (--vgdb-error=1), a newbie (i.e. my students) can have difficulties to understand as

Re: [Valgrind-users] Cache conflict detection support in cachegrind

On 29-01-23 20:50, Ivica B wrote: Hi Paul! I read the info you provided, but none of the programs actually support detecting cache conflicts. Hi No, the tools I suggested would only give an indication, you would then have to use your code knowledge and maybe some trial and error to make

Re: [Valgrind-users] thread not created when program executed with valgrind

On 16/01/2024 20:17, JD Silence wrote: Hello, I'm looking for some hints, advice and any other things that could help me figure this out. I have a big program which I wanted to debug some memory issues. This program internally creates and runs several threads. [snip] The program is

Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing

> On 22 Apr 2024, at 20:40, Carl Love via Valgrind-users > wrote: > > Mark: > > The PowerPC test results for Valgrind 3.23.0.RC1 > > --- > Power 10, Fedora release 38 : > > memcheck/tests/linux/rfcomm (stderr) also

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

On 25-04-24 19:09, Simon Sobisch wrote: Am 25.04.2024 um 20:55 schrieb Paul Floyd via Valgrind-users: On 25-04-24 14:39, Simon Sobisch wrote: 3. compile warnings with clang on arm64 (in multiple files/positions with different arguments to the macros CALL_FN_W_W, CALL_FN_W_WW

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

On 25-04-24 14:39, Simon Sobisch wrote: 1. Several failing tests because of sed and ps usage. With 2.  Two failing tests on Debian with AMD Ryzen: 3. compile warnings with clang on arm64 (in multiple files/positions with different arguments to the macros CALL_FN_W_W, CALL_FN_W_WW,

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

On 25-04-24 08:50, Simon Sobisch wrote: I've compiled and tried to run the RC2 on some environments, using 1. Find just a minor patch for configure.ac to improve help output and keep the style of the file (two missing spaces visible in "configure --help"; tabs/line breaks). 2. One thing

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

On 24-04-24 23:33, Mark Wielaard wrote: An RC2 tarball for 3.23.0 is now available at FreeBSD amd64 and arm64 both still fine. A+ Paul ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net

Re: [Valgrind-users] Always investigate valgrind memcheck errors [rjo...@redhat.com: Re: xz backdoor]

On 30-03-24 11:43, Mark Wielaard wrote: For those of you tracking the xz backdoor: https://lwn.net/Articles/967180/ valgrind plays a little role in the discovery. "Then recalled that I had seen an odd valgrind complaint in my automated testing of postgres, a few weeks earlier, after some

Re: [Valgrind-users] Docker Support

On 04-03-24 11:42, jinesh gada wrote: Hi Everyone, I am working on integrating a docker based application on a virtual machine with Valgrind. I have bind the Valgrind libraries and required folder structure with the container. But on running my app with Valgrind I'm facing an issue

Re: [Valgrind-users] Semaphore error on Helgrind and Drd?

On 25/05/2024 12:29, Paulo Ferreira wrote: > Error message from Helgrind: > > $ valgrind --tool=helgrind ./prog > ... > ==6587== Thread #1: Bug in libpthread: sem_wait succeeded on semaphore > without prior sem_post > ==6587==at 0x4850069: sem_wait_WRK (hg_intercepts.c:3155) > ==6587==