On 4/24/25 03:59, Mark Wielaard wrote:
An RC2 tarball for 3.25.0 is now available at
https://sourceware.org/pub/valgrind/valgrind-3.25.0.RC2.tar.bz2
(md5sum = 4e53a0a1a8d1404e77e6c45015eeb472)
(sha1sum = ba482eeeb89dd271006f59b09f01048be6530a53)
https://sourceware.org/pub/valgrind/valgrind-3.25
On 4/20/25 04:13, Sean McBride wrote:
On 19 Apr 2025, at 12:48, Paul Floyd via Valgrind-users wrote:
I'll give macOS a go shortly.
macOS? It hasn't been supported in years, unless I missed some exciting news?
macOS is lagging far behind. In the last 6 months I made 4 changes f
On 19-04-25 16:48, Paul Floyd via Valgrind-users wrote:
On 4/18/25 15:53, Mark Wielaard wrote:
Slightly later than originally planned, but the RC1 is finally out!
Hi Mark
There was one small regtest issue on FreeBSD (a script missing from
dist_noinst_SCRIPTS in none/tests/freebsd
On 4/18/25 15:53, Mark Wielaard wrote:
Slightly later than originally planned, but the RC1 is finally out!
Hi Mark
There was one small regtest issue on FreeBSD (a script missing from
dist_noinst_SCRIPTS in none/tests/freebsd/Makefile.am). It's not a
blocking issue and it should now be fixe
On 21/03/2025 09:06, kiran hardas wrote:
Hi Paul/Team,
Thank you for your suggestion. I added the entry for shmget function
in coregrind/m_syswrap/syswrap-x86-linux.c
and the error got resolved for shmget function. Yes it is x86 linux
that is getting used. Similar errors came for shmat, shmdt
On 3/21/25 09:06, kiran hardas wrote:
Hi Paul/Team,
Thank you for your suggestion. I added the entry for shmget function
in coregrind/m_syswrap/syswrap-x86-linux.c
and the error got resolved for shmget function. Yes it is x86 linux
that is getting used. Similar errors came for shmat, shmdt, s
On 3/12/25 22:40, kiran hardas wrote:
Hi Philippe/Team,
Thank you Philippe for your suggestions, I was able to resolve the
earlier errors by adding additional valgrind options and loading the
symbol table.
In my application, few variables and a function pointer was
uninitialised which led to
On 10-02-25 09:44, Lev Yudalevich wrote:
My first PC has i7-6700K @ 4.00GHz x 8 CPU, 32GiB RAM
My second PC has i7-10700 @ 2.90GHz x 16 CPU, 64GiB RAM
Both machines have identical OS installation (Ubuntu 22.04.5 LTS) rest
of the software (toolchains etc).
However, running Valgrind (version 3.
> On 11 Feb 2025, at 04:38, Jessica Long wrote:
>
> Not sure what to do. I'm new to Linux and Valgrind.
>
> I'm on CLion, and I'm trying to run my code with Valgrind memcheck. However
> I get the message.
>
> --33110:0:libcfile Valgrind: FATAL: Private file creation failed.
>The curre
On 14-12-24 04:11, John Reiser wrote:
I've tried to build the last release but have not resolved the place
why it tries to link against the non-existing libc and how to fix that...
Here are some workarounds:
I'm trying to build valgrind (memcheck) for 32-bit programs on Android
running under
On 13/12/2024 16:26, Simon Sobisch wrote:
Daear valgrind users and devs,
Valgrind-3.22.0 and asserts reproducible on
aarch64-unknown-linux-android (with several applications) as follows:
valgrind:
/home/builder/.termux-build/valgrind/src/coregrind/m_redir.c:796 (void
vgPlain_redir_add_ifun
On 05-12-24 14:19, Wojciech Bocer wrote:
Hello,
I have a problem with Valgrind taking a lot of time trying to
determine if there are memory leaks before it exits.
Roughly speaking leak detection involves scanning though all accessible
memory using pointer-size alignment to look for any po
On 15-11-24 08:34, Mathew T wrote:
Hello,
I’m seeking assistance with a challenging issue involving an
executable on an ARM64 Ubuntu system. Here’s the problem and what I’ve
done to investigate it so far:
Problem Summary: I have an ARM64 executable that crashes with a
segmentation fault(early
On 12-11-24 22:22, William Chan (BLOOMBERG/ 919 3RD A) wrote:
Hi,
I have a program that induces a possibly lost warning via an interior
pointer but I deallocate the pointer properly. Is Valgrind supposed to
be able to know that an interior pointer is freed? I'm trying to
determine whether
On 26-10-24 13:36, Daniel Feenberg wrote:
This is very disappointing. Such moves may be frequent in other
languages, but I don't see it happening to much in my Fortran 95 code. I
suppose if subroutine arguments are copy-in/copy-out, that would be a
source of spurious messages, as could
On 24-10-24 14:33, Daniel Feenberg via Valgrind-users wrote:
I am a bit inexperienced with Valgrind which reports an uninitialized
variable in my 34,000 line program. But the message comes from a branch
deep in libgfortran. After some experimentation, I created the following
example program
On 10-09-24 06:59, Tech info wrote:
We are debugging memory leaks in our legacy 32-bit multithreaded
applications on ARM64-bit processors, but we're facing performance
issues with Valgrind:
*Application Crash*: After 9-10 minutes, the application crashes,
and |top commands|showsno a
> On 5 Sep 2024, at 11:18, Isharat Mahmood wrote:
>
> Dear Team,
>
> We have a query regarding Valgrind working model.
> Is it the right mailer list to ask?
If it is a Valgrind User question then this is the right list.
Otherwise there is a mailing list for Valgrind developers.
A+
Paul
On 06-06-24 15:43, Byron Hawkins wrote:
For the purposes of studying dead-code elimination in LLVM, I'd like to
generate a simple list of all the functions that are ever called by the
target program. There's no need for any timing or frequency reports or
backtraces or any other details. So fa
On 04-07-24 14:26, Thomas Wollenzin wrote:
Hi,
I was wondering whether there are other ways of communication for the
Valgrind community. In particular I'm thinking Slack or Discord?
The main problem that I see with these platforms is that the perceived
ease of access means that there are
On 23-06-24 15:43, Mark Wielaard wrote:
Hi all,
On Thu, Nov 16, 2023 at 08:22:33PM +0100, Mark Wielaard wrote:
Valgrind is more than 20 years old and we have been collecting
bugs slightly faster than we have been able to close them. Which means
we now have around a thousand bugs open. This i
On 19-06-24 08:15, Thomas Wollenzin wrote:
Thanks for the hint, Sean.
While that might work perfectly fine, I'm personally not a big fan of
these types of tools. They're fine for proofing a theory but shouldn't
be used to 'cover up' developer mistakes. Code should be written as
solidly as p
On 17-06-24 08:45, Thomas Wollenzin wrote:
Hi,
I have a questing regarding Valgrind report 'Mismatched free() / delete
/ delete []'.
I understand that Valgrind is redirecting calls to new/delete and so on
to its own. On the allocation side I see:
operator new(unsigned long) (vg_repl
On 15-06-24 17:38, Thomas Wollenzin wrote:
Hi,
I'm not too familiar with valgrind yet so excuse a potentially dumb
question.
I'm trying to fix an issue in our code base that valgrind reported as
'Conditional jump or move depends on uninitialised value(s)'. In
particular I have a hard tim
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==
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==
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
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
https://lists.sourceforge.net/lists/lis
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 th
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,
CALL_FN_
> 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 fail
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 pac
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 sayi
33 matches
Mail list logo
