Re: [Valgrind-users] alternative ways of communication

Hi Thomas, On Thu, 2024-07-04 at 14:26 +, Thomas Wollenzin wrote: > I was wondering whether there are other ways of communication for the > Valgrind community. We do have mailinglists. And there is an IRC channel for Valgrind developers: #valgrind-dev at irc.libera.chat but users are also

Re: [Valgrind-users] [Valgrind-developers] A thousand bugs

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 is a slightly > intimidatin

Re: [Valgrind-users] Question regarding 'Conditional jump or move depends on uninitialised value(s)'

On Wed, Jun 19, 2024 at 08:07:09PM +, Paul Floyd via Valgrind-users wrote: > 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 >

[Valgrind-users] Valgrind-3.23.0 is available

We are pleased to announce a new release of Valgrind, version 3.23.0, available from https://valgrind.org/downloads/current.html. See the release notes below for details of changes. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time,

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

Andreas Arnez (1): s390x: Improve operand names in trackers for PRNO Mark Wielaard (11): 32 bit new_delete_mismatch_size and sized_aligned_new_delete_misaligned .exp Add new .exp-32 files to memcheck/tests/Makefile.am EXTRA_DIST filter out in /absolute/path in drd/tests stderr filter Filter

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

t of the stacktrace is slightly different on different systems. I tried to work around that with the following commit: commit 04d30049bf9b4ae14262a50e8a16442e1edf75f8 Author: Mark Wielaard Date: Tue Apr 23 14:14:33 2024 +0200 Filter away "main" differences in filter_fdleak St

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

Test results look fairly good on the platforms I tested. I did fix a couple of small (testcase) issues for x86: 32 bit new_delete_mismatch_size and sized_aligned_new_delete_misaligned .exp and s390x: filter out in /absolute/path in drd/tests stderr filter With those: RHEL 8.9/x86-64: ==

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

An RC1 tarball for 3.23.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.23.0.RC1.tar.bz2 (md5sum = 6d36fd8981d6aab7350f12cc61973be5) (sha1sum = 6ff57d5981d774e446853e8b166be8a3bb324601) https://sourceware.org/pub/valgrind/valgrind-3.23.0.RC1.tar.bz2.asc Please give it a try

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

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 package updates were installed."

[Valgrind-users] FOSDEM 2024, Debuggers and Analysis tools devroom

Hi valgrind hackers and users, Fosdem is Saturday and Sunday, 3 & 4 February, in Brussels. It is a great conference to hear about various technical topics and to meet others. In the Debuggers and Analysis tools devroom there will also be a talk from Bruno Lathuilière about Verrou : a valgrind

[Valgrind-users] A thousand bugs

Hi all, 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 is a slightly intimidating number. But some of the bugs are more than 10 years old (the oldest bugs are from

[Valgrind-users] Valgrind-3.22.0 is available

We are pleased to announce a new release of Valgrind, version 3.22.0, available from https://valgrind.org/downloads/current.html. See the release notes below for details of changes. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time,

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

Hi Eyal, On Fri, 2023-10-27 at 21:44 -0600, Eyal Soha wrote: > I have uploaded two possible fixes but I'm unable to test them.  If someone > is able to reproduce this bug faithfully, can you try each patch below and > let me know if it works?  You can apply the patch with `git am '. > >

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

Hi, On Thu, Oct 26, 2023 at 12:38:04PM -0700, Carl Love via Valgrind-developers wrote: > Valgrind-3.22.0.RC2 looks good on power. I have run the RC2 on Power > 10LE, Power 9 LE, Power 8 LE/BE, and Power 7 BE. I see the two failures > > memcheck/tests/bug340392 (stderr) >

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

bit SIMD tests for s390x in vbit-test Carl Love (3): Bug 476025 - Powerpc, update expected results for the vbit-test Revert "Bug 476025 - Powerpc, update expected results for the vbit-test" Change the vbit test specification for Iop_CmpGT64Ux2 Mark Wielaard (7): A

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

Hi, On Wed, Oct 18, 2023 at 01:04:21AM +0200, Mark Wielaard wrote: > An RC1 tarball for 3.22.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2 > (md5sum = 786715e301f9b1d3e10faf2a5b360598) > (sha1sum = ea0e9ca5b5c45168bfcb795e1d19d9d3f5d58

[Valgrind-users] Valgrind-3.22.0.RC1 is available for testing

An RC1 tarball for 3.22.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2 (md5sum = 786715e301f9b1d3e10faf2a5b360598) (sha1sum = ea0e9ca5b5c45168bfcb795e1d19d9d3f5d58223) https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc Please give it a try

Re: [Valgrind-users] getting type information for local and global variables?

Hi Tia, On Wed, Aug 02, 2023 at 10:27:10AM -0500, Tia Newhall wrote: > First, sorry but I'm cutting and pasting below your response from off the > list archive below since I didn't receive an email with your reply. email is a little unreliable these days :{ And then I went on vacation. So

Re: [Valgrind-users] getting type information for local and global variables?

Hi Tia, On Tue, 2023-08-01 at 08:56 -0500, Tia Newhall wrote: > I'm building a valgrind tool, and as part of its functionality I need to get (and ultimately print out) local and global variable values based on their C types. However, I do not see a way to get detailed type information for locals

Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64

Hi Simon, On Thu, Jun 29, 2023 at 05:46:59PM +0200, Simon Sobisch wrote: > Am 29.06.2023 um 15:10 schrieb John Reiser: > >>Running valgrind on GnuCOBOL errors out with > >> > >>vex amd64->IR: unhandled instruction bytes: > >>  0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48 0xC7 0x5 0x6F > >>vex amd64->IR:  

[Valgrind-users] Valgrind-3.21.0 is available

We are pleased to announce a new release of Valgrind, version 3.21.0, available from https://valgrind.org/downloads/current.html. See the release notes below for details of changes. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time,

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

An RC2 tarball for 3.21.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC2.tar.bz2 (md5sum = f33407fdffbfa78f5014781cc92297cf) (sha1sum = c520ee0c28d9e20d28aa25d05ce2525c39a69135) https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC2.tar.bz2.asc Please give it a try

Re: [Valgrind-users] unhandled instruction bytes

On Wed, Apr 19, 2023 at 11:46:34AM +0200, folkert wrote: > > > The 2 calls it does are: > > > > > > print_char: > > > movb (%esi), %al > > > movb %al, buffer > > > movl $4, %eax > > > movl $1, %ebx > > > movl $buffer, %ecx > > > movl $1, %edx > > > int $0x80 >

[Valgrind-users] Valgrind-3.21.0.RC1 is available for testing

An RC1 tarball for 3.21.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2 (md5sum = a3c7eeff47262cecdf5f1d68b38710b7) (sha1sum = 46fc5898415001e045abc1b4e2909a41144ed9c4) https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2.asc Please give it a try

[Valgrind-users] A bit more (pre-release) automation

Hi, Working towards a new release (3.21.0 currently planned for April 28) there is a bit more automation to show pre-releases and documentation: https://snapshots.sourceware.org/valgrind/trunk/ Every 15 minutes a buildbot will check for new commits and create a dist, html manual pages and

Re: [Valgrind-users] Timer delete

On Sat, Nov 12, 2022 at 12:46:41PM +0100, Philippe Waroquiers wrote: > On Sat, 2022-11-12 at 12:21 +0100, Paul Floyd wrote: > > So my conclusion is that there are two problems > > 1. Some cleanup code missing in __libc_freeres that is causing this leak > > (libc problem) > > 2. no-stackcache not

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

Hi Mathieu, On Fri, Oct 21, 2022 at 08:20:01AM +0200, Mathieu Malaterre wrote: > Could someone apply the following patch: > > sed -i -e 's/cortex-a8/generic-armv7-a/g' Makefile.all.am > > ref: > https://bugs.kde.org/show_bug.cgi?id=456200 Sorry this didn't make the release. I would have to

[Valgrind-users] Valgrind-3.20.0 is available

We are pleased to announce a new release of Valgrind, version 3.20.0, available from https://valgrind.org/downloads/current.html. See the release notes below for details of changes. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time,

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

Hi Philippe, On Sat, Oct 22, 2022 at 02:58:28PM +0200, Philippe Waroquiers wrote: > I have started running valgrind on valgrind (outer/inner setup). > Results should be available tomorrow evening or so ... > For the first few tests, seems ok. > > Just one strange thing: > The outer valgrind

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

se. I added the touch to the testcases as attached. That makes sure the cgout-test file is always newer. Cheers, Mark >From 206dbcfed93f22370e03a03dd07f14ab675e24a8 Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Sat, 22 Oct 2022 17:29:00 +0200 Subject: [PATCH] {callgrind,callgrind}/tests/ann{1,2}.vgtest touch

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

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 issues are reported, the 3.20.0 final release will

Re: [Valgrind-users] new error message from Valgrind

Hi, On Wed, Aug 03, 2022 at 05:32:56PM +0100, Tom Hughes wrote: > No, it's clone3: > > https://bugs.kde.org/show_bug.cgi?id=420906 So please upgrade to valgrind 3.18.0 or higher (latest is 3.19.0). Cheers, Mark ___ Valgrind-users mailing list

Re: [Valgrind-users] new error message from Valgrind

; It's harmless - the next version of valgrind will silently > reject it with ENOSYS which is what is happening now anyway > just with a warning. Where the next version of valgrind is 3.19.0 which is already released (in April). So you might just want to upgrade your valgrind. If you want to ba

[Valgrind-users] Happy birthday, Valgrind!

It has been twenty years today since Valgrind 1.0 was released. Make sure to read Nicholas Nethercote’s Twenty years of Valgrind: https://nnethercote.github.io/2022/07/27/twenty-years-of-valgrind.html And learn about the early days, Valgrind "skins", the influence Valgrind had on raising the bar

Re: [Valgrind-users] How to do handle SIGILL nostop in valgrind?

Hi Ellie, On Sun, Jun 26, 2022 at 10:13:37AM +0200, ellie wrote: > How do I run openssl programs in valgrind on processors where it causes > SIGILL? https://www.openssl.org/docs/faq.html#PROG17 > > They recommend to use handle SIGILL nostop, but the only mention in the > valgrind documentation

Re: [Valgrind-users] Question: bug in user code, valgrind or glibc?

d(VGO_freebsd) > STRNCMP(VG_Z_LIBC_SONAME, strncmp) This looks like https://bugs.kde.org/show_bug.cgi?id=434764 iconv_open causes ld.so v2.28+ to use optimised strncmp Which was recently (but after 3.19.0) fixed by merging this commit: commit 947388eb043ea1c44b37df94046e1eee790ad776 Author:

[Valgrind-users] Valgrind-3.19.0 is available

We are pleased to announce a new release of Valgrind, version 3.19.0, available from https://valgrind.org/downloads/current.html. 3.19.0 fixes a number of bugs and was tested against glibc-2.35, gcc-12 (pre-release) and linux 5.17.1 on GNU/Linux systems and tested on various FreeBSD systems. See

[Valgrind-users] Fosdem Talks, next release & developer meetup

and debuginfo, Mark Wielaard https://fosdem.org/2022/schedule/event/valgrind_debuginfo/ - Valgrind on RISC-V, Petr Pavlu https://fosdem.org/2022/schedule/event/valgrind_riscv/ - Adding Power ISA 3.1 instruction support, Carl Love https://fosdem.org/2022/schedule/event/valgrind_isa31/ Unfortunately

Re: [Valgrind-users] does Valgrind-3.19.0.GIT support Clang14 dwarf 5?

On Wed, Feb 16, 2022 at 12:46:32PM +0900, ISHIKAWA,chiaki wrote: > This is tangent to the original question, but this part: > > > with split-dwarf (which rnglistx and strx > form codes doesn't support yet) > > valgrind does support bulk of data generated by --split-dwarf (gcc), > doesn't it? No,

Re: [Valgrind-users] does Valgrind-3.19.0.GIT support Clang14 dwarf 5?

Hi Thomas, On Sun, Feb 13, 2022 at 08:18:48PM +, Thomas Wollenzin wrote: > This is a just a quick question. As I haven't found a sufficient answer in > the archives. > Does Valgrind-3.19.0.GIT support Clang14's dwarf5 yet? > > Compiling my application with '-gfull -gdwarf-4 -gdwarf64'

[Valgrind-users] Virtual Valgrind Fosdem Devroom, Sun 6 Feb

and debuginfo, Mark Wielaard 16:30-16:55 Valgrind on RISC-V, Petr Pavlu 17:00-17:25 Adding Power ISA 3.1 instruction support, Carl Love 17:30-18:00 20 years of Valgrind, Celebration, Julian Seward All times are as if the the conference was in Brussels (CET/UTC+1) The last session, 20 years of Valgrind

Re: [Valgrind-users] [Valgrind-developers] Virtual Valgrind Fosdem Devroom

ginal call for participation below. On Mon, Dec 13, 2021 at 06:04:33PM +0100, Mark Wielaard wrote: > Hi valgrind hackers, > > Valgrind will participate in the Virtual Fosdem on Sunday 6 February > 2022 https://fosdem.org/2022/schedule/track/valgrind/ > > We would like to in

[Valgrind-users] Virtual Valgrind Fosdem Devroom

Hi valgrind hackers, Valgrind will participate in the Virtual Fosdem on Sunday 6 February 2022 https://fosdem.org/2022/schedule/track/valgrind/ We would like to invite people to propose talks on valgrind by submitting a talk proposal to https://penta.fosdem.org/submission/FOSDEM22 Please select

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

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 are important for you and report any problems

Re: [Valgrind-users] Very slow execution under Fedora 34

Hi, On Sun, 2021-09-05 at 20:29 -0300, Alvaro Kuolas wrote: > I am running valgrind on my PC with dual boot Windows 10 and Fedora > 34. > > Running the same test on Ubuntu 20.04 (under Windows 10 WSL2) > valgrind runs > in less than a second, but on Fedora 34 is very slow, several minutes >

[Valgrind-users] Valgrind-3.17.0 is available

We are pleased to announce a new release of Valgrind, version 3.17.0, available from http://valgrind.org/downloads/current.html. The source tarball is signed with the PGP key at the bottom of this message. 3.17.0 fixes a number of bugs and adds some functional changes: support for GCC 11, Clang

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

Hi Carl, On Wed, 2021-03-17 at 09:36 -0700, Carl Love wrote: > On Wed, 2021-03-17 at 13:08 +0100, Mark Wielaard wrote: > The testing on the ISA 3.1 because the file > none/tests/ppc64/isa_3_1_register_defines.h is missing from RC2. I > checked and it is also missing from RC1. T

[Valgrind-users] Valgrind-3.17.0.RC2 is available for testing

Greetings. A second release candidate for 3.17.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.17.0.RC2.tar.bz2 (md5 = 5dcf7c42635e19b074714c53f3a57580) Thanks for the testing of RC1. The changes between RC1 and RC2 are minimal: - debuginfod-check.pl is now included to fix make

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

Hi Paul, On Tue, Mar 16, 2021 at 09:07:56PM +0100, Paul Floyd wrote: > > 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/valgri

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

Hi Carl, On Mon, 2021-03-15 at 11:33 -0700, Carl Love wrote: > Will Schmidt posted an email with regards to the build issue: > >I think so.. we ran into a similar issue late last year, which I >think >we had determined was due to the MPI packages in the > environment. >The

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

Hi Carl, On Mon, 2021-03-15 at 09:05 -0700, Carl Love wrote: > I am seeing issues on various power platforms. > > Power 8 BE > >gcc --version >gcc (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5) > >more /etc/os-release >NAME=Fedora >VERSION="27 (Server Edition)" >ID=fedora >

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

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 are reported, the 3.17.0 final release will

Re: [Valgrind-users] License Question

Hi, On Sun, Nov 08, 2020 at 01:06:39PM -0500, Rayce West wrote: > After researching GGPL some, I'm wondering how it's possible that angr (and > pyvex) are allowed to use BSD licenses when they integrate VEX as their > lifter and IR, especially since it's the General and not the Lesser? It is

Re: [Valgrind-users] Use of valgrind with microthreading

Hi Shachar, On Fri, Aug 14, 2020 at 06:35:14PM +0300, Shachar Shemesh wrote: > I am writing my own C++ microthreading library. At the very first switch, I > get the following message from Valgrind: > > ==15122== Warning: client switching stacks?  SP change: 0x1ffeffe788 --> > 0x75d0f80 >

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

Hi, On Tue, 2020-05-19 at 14:32 +0200, Julian Seward wrote: > A first release candidate for 3.16.0 is available at > https://sourceware.org/pub/valgrind/valgrind-3.16.0.RC2.tar.bz2 > (md5 = 21ac87434ed32bcfe5ea86a0978440ba) > > Please give it a try on platforms that are important for you. If no

Re: [Valgrind-users] Unable to start process with valgrind, failing with setns

Hi Bhargav, On Mon, Mar 16, 2020 at 10:44:42AM +0530, bhargav p wrote: > I am trying to start a process with valgrind. In my code, I am using setns > call. > > When I start process with valgrind, seeing below error and process is > getting exited. > > "Failed to switch to namespace ns1:

[Valgrind-users] [FOSDEM] [CfP] Debugging Tools devroom 2020

* Last Reminder! Talk proposal deadline is this weekend! * Debugging Tools developer room at FOSDEM 2020 (Brussels, Belgium, February 2). Talk/Discussion Submission deadline: Sunday1 Dec 2019 Devroom Schedule announcement: Sunday 15 Dec 2019 Devroom day:

[Valgrind-users] [FOSDEM] [CfP] Debugging Tools devroom 2020

Debugging Tools developer room at FOSDEM 2020 (Brussels, Belgium, February 2). Talk/Discussion Submission deadline: Sunday1 Dec 2019 Devroom Schedule announcement: Sunday 15 Dec 2019 Devroom day: Sunday2 Feb 2020 FOSDEM is a free software

[Valgrind-users] [FOSDEM] [CfP] Debugging Tools devroom 2020

Debugging Tools developer room at FOSDEM 2020 (Brussels, Belgium, February 2). Talk/Discussion Submission deadline: Sunday1 Dec 2019 Devroom Schedule announcement: Sunday 15 Dec 2019 Devroom day: Sunday3 Feb 2020 FOSDEM is a free software

Re: [Valgrind-users] No Git tag for v3.15.0

Hi Mike, On Mon, 2019-09-09 at 14:09 +0100, Mike Crowe wrote: > The Valgrind Git repository at > https://sourceware.org/git/?p=valgrind.git > has a VALGRIND_3_14_0 tag, but no tag corresponding to the 3.15.0 > release. > It looks like the tag should reference >

Re: [Valgrind-users] --track-origins option is not working

On Tue, 2019-07-02 at 15:58 +0530, subhasish Karmakar wrote: > Hi Julian, > "/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so" file is still > stripped > even after rebuilding. > Could you please suggest some way to resolve this issue. A normal build doesn't remove debug information. How did you

Re: [Valgrind-users] Master and -Wformat-overflow warning

Hi Jeffrey, On Thu, May 02, 2019 at 12:46:30PM -0400, Jeffrey Walton wrote: > On Thu, May 2, 2019 at 12:02 PM Mark Wielaard wrote: > > > > On Tue, 2019-04-30 at 20:43 -0400, Jeffrey Walton wrote: > > > It looks like GCC has one squawk: > > > > > > vgd

Re: [Valgrind-users] Master and -Wformat-overflow warning

Hi Jeffrey, On Tue, 2019-04-30 at 20:43 -0400, Jeffrey Walton wrote: > It looks like GCC has one squawk: > > vgdb.c: In function ‘standalone_send_commands’: > vgdb.c:1008:21: warning: ‘%02x’ directive writing between 2 and 8 > bytes into a r > egion of size 3 [-Wformat-overflow=] >

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

On Tue, 2019-04-09 at 09:02 +0200, Mark Wielaard wrote: > Hi, > > On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > > A first release candidate for 3.15.0 is available at > > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > > (md5 = 56d9f

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

On Mon, 2019-04-08 at 10:25 -0700, Carl Love wrote: > I have run RC1 on Power 7, Power 8 LE, Power 8 BE and Power 9 and > noted each system the same four post errors that I did not see last > week when I tested patches to be committed. The errors are: > > cachegrind/tests/ann1

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

Hi, On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > A first release candidate for 3.15.0 is available at > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > (md5 = 56d9f5e25615d48110da0aa5764d481e) > > Please give it a try on platforms that are important for you. If no

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

On Wed, Oct 03, 2018 at 05:53:57PM +0200, Julian Seward wrote: > Per the subject line, valgrind-3.14.0.RC2 is available for testing, at: > > ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > (md5 =

Re: [Valgrind-users] Off-topic: what happended to bzip.org?

Hi Jeffrey, Unfortunately the bzip.org domain is no longer available to the bzip2 project. The plan is to move back to sourceware: https://sourceware.org/bzip2/ https://sourceware.org/pub/bzip2/ And also setup a git repo, bugzilla, mailinglist, etc. for the project there. But not everything has

Re: [Valgrind-users] Is there a Valgrind that knows arm64/aarch64?

On Sat, 2018-06-16 at 21:30 -0400, Alan Corey wrote: > OK, thanks, I ran Valgrind 3.13.0 on a 32-bit Raspberry Pi and it > worked fine.  Found bugs anyway.  KDE and Fedora are way off my beaten > path.  Oh, I see even Raspbian Stretch finally got 3.13, they had one > that didn't do arm at all.

Re: [Valgrind-users] Is there a Valgrind that knows arm64/aarch64?

On Sat, 2018-06-16 at 19:09 -0400, Alan Corey wrote: > > Linux version 4.16.0-2-arm64 (debian-ker...@lists.debian.org) (gcc > version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) > > The Valgrind was a 3.13.0 that I'd built from the distribution > tarball, then I discovered the

Re: [Valgrind-users] Please leave Sorceforge

On Sun, May 20, 2018 at 02:44:16PM -0400, Jeffrey Walton wrote: > When signing up for the newsletter we have to " I agree to receive > these communications from SourceForge.net" Requiring me to accept > spam is very disingenuous. > > Please leave Sorceforge. We could ask the sourceware

Re: [Valgrind-users] problems with Ubuntu 17.10

On Fri, Jan 05, 2018 at 09:36:16AM -0800, Mark Roberts wrote: > On Tue, Jan 02, 2018 at 02:39:36PM -0800, Mark Roberts wrote: > > The problem with valgrind/memcheck/tests/linux/stack_changes.c > > appears to be an actual problem with the source. In June of > > 2017 the gnu c header file

Re: [Valgrind-users] problems with Ubuntu 17.10

On Tue, Jan 02, 2018 at 02:39:36PM -0800, Mark Roberts wrote: > The problem with valgrind/memcheck/tests/linux/stack_changes.c appears > to be an actual problem with the source. In June of > 2017 the gnu c header file sys/ucontext.h was changed. > typedef struct ucontext is now typedef struct

[Valgrind-users] [FOSDEM] Call for Participation: Debugging Tools DevRoom at FOSDEM 2018

day1 Dec 2017 Devroom Schedule announcement: Friday 15 Dec 2017 Devroom day: Saturday 3 Feb 2018 Hope to see you all at FOSDEM 2018 in the joint Debugging Tools devroom. Brussels (Belgium), Saturday February 3th 2018. On behalf of the devroom c

[Valgrind-users] [FOSDEM] Call for Participation: Debugging Tools DevRoom at FOSDEM 2018

On Fri, 2017-10-13 at 12:37 +0200, Ivo Raisr wrote: > Debugging Tools developer room at FOSDEM 2018 > (Brussels, Belgium, February 3th). > [...] > ** How to Submit > > There are two ways. > The first one is to use the FOSDEM 'pentabarf' tool to submit your > proposal: >

Re: [Valgrind-users] [Valgrind-developers] Migrating Valgrind sources from SVN to GIT

On Fri, 2017-08-04 at 21:58 +0200, Mark Wielaard wrote: > > How the test migration was performed: > > ~~ > > See recipes at https://github.com/ivosh/valgrind-git-migration > > I'll follow that to recreate the git repository with all br

Re: [Valgrind-users] Migrating Valgrind sources from SVN to GIT

On Fri, Aug 04, 2017 at 08:14:19PM +0200, Ivo Raisr wrote: > Where I will find the new repo: > ~~~ > At sourceware.org. Precisely at: > git://sourceware.org/git/valgrind.git/ > http://sourceware.org/git/valgrind.git/ > Right now a snapshot of SVN sources as of 2017-06-26 is

Re: [Valgrind-users] Source for previous versions of valgrind

On Thu, 2017-07-06 at 08:05 -0700, John Reiser wrote: > On 07/06/2017 @1457Z, Mark Wielaard wrote: > > On Thu, 2017-07-06 at 13:24 +, Phil Longstaff wrote: > >> Where can I find source tarballs for 3.11.0 and 3.12.0? > > > > http://valgrind.org/downloads/old

Re: [Valgrind-users] Source for previous versions of valgrind

On Thu, 2017-07-06 at 16:57 +0200, Mark Wielaard wrote: > On Thu, 2017-07-06 at 13:24 +, Phil Longstaff wrote: > > Where can I find source tarballs for 3.11.0 and 3.12.0? > > http://valgrind.org/downloads/old.html O, they are not linked from that page. Sorry. But they

Re: [Valgrind-users] Source for previous versions of valgrind

On Thu, 2017-07-06 at 13:24 +, Phil Longstaff wrote: > Where can I find source tarballs for 3.11.0 and 3.12.0? http://valgrind.org/downloads/old.html -- Check out the vibrant tech community on one of the world's most

Re: [Valgrind-users] Valgrind 3.13.0 tarball hosted at sourceware.org - legit or not?

On Fri, 2017-06-16 at 08:05 -0400, Zhiming Wang wrote: > According to the download page > , the tarball of the 3.13.0 is > hosted at sourceware.org > (). Is this legit? > Just want to make

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

Hi Users (redirected from valgrind-developers), On Fri, 2017-06-02 at 17:57 +0200, Julian Seward wrote: > An RC1 tarball for 3.13.0 is now available at > ftp://sourceware.org/pub/valgrind/valgrind-3.13.0.RC1.tar.bz2 > (md5sum = a94957849869f1e50a16d60737cfcc29) > > Please give it a try in

Re: [Valgrind-users] [Valgrind-developers] Fosdem devroom and Valgrind Hackaton

, 2016 at 01:46:39PM +0100, Mark Wielaard wrote: > Hi Valgrind users, hackers and enthusiasts, > > We have program from the valgrind devroom that will take place during > Fosdem in Brussels on Saturday 5 February 2017: > https://fosdem.org/2017/schedule/track/valgrind/ >

[Valgrind-users] Fosdem devroom and Valgrind Hackaton

discussed. Discuss any kind of possible improvement (technical or functional) to Valgrind. If you want to put something on the agenda please send a small description (one or two paragraphs) to the the moderator Mark Wielaard m...@redhat.com with in the subject: "FOSDEM devroom di

Re: [Valgrind-users] Spurious Assertion from valgrind

On Wed, 2016-10-19 at 09:29 -0400, Eric Chamberland wrote: > I recently upgraded to valgrind 3.11.0 (was 3.8.1 before). > I also upgraded Intel MKL to the 2015 version. > > We use valgrind since 2011-10-27 to test our code nightly with about > 2200 tests. > > Since this upgrade, some tests (not

Re: [Valgrind-users] [Valgrind-developers] AVX-512 support inquiry

On Wed, 2016-09-07 at 10:23 +0200, Julian Seward wrote: > A good description of the instruction set is also necessary. Is that > publically available? It seems Intel moves it around from time to time, because my old bookmarks don't work anymore. But I found a recent description of avx-512 at

Re: [Valgrind-users] Unrecognized instruction in libgcrypt PRNG

On Wed, 2016-08-24 at 22:50 +0200, Markus Teich wrote: > When can we expect a new release containing the fix? 3.11.0 > is nearly a year old now. Hopefully in ~3 weeks. But Julian is the release master and he is away this week. So when he returns he might give you a slightly different estimate.

Re: [Valgrind-users] Unrecognized instruction in libgcrypt PRNG

On Wed, 2016-08-24 at 07:42 -0700, John Reiser wrote: > Markus Teich wrote: > > > vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 > > 0xFF 0xC9 > > vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 > > vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F > > vex

Re: [Valgrind-users] expected results for regtest

On Fri, Apr 15, 2016 at 09:38:03AM +0200, Ivo Raisr wrote: > 2016-04-15 2:56 GMT+02:00 John Reiser : > > = massif/tests/new-cpp.post.diff (post) > > - 1 4,0084,0084,000 8 > > 0 > > - 2 8,0168,016

[Valgrind-users] Fosdem 2015 talk slides online

Hi all, All the slides of the talks given in the Valgrind devroom at Fosdem in Brussel this year are now online: https://fosdem.org/2015/schedule/track/valgrind/ Sadly we had some trouble producing videos of the talks. If by a miracle we did manage to record some they will appear here with the

[Valgrind-users] FOSDEM valgrind devroom schedule posted (Brussels, Saturday 31 Jan 2015)

paths Julian Seward 16:00 - 17:00 How to start hacking on Valgrind by example Mark Wielaard 17:00 - close Valgrind Hackaton Hope to see you all in Brussels, Saturday 31 January. -- New Year. New

[Valgrind-users] FOSDEM Valgrind dev-room - Brussels, 31 Jan 2015 - DEADLINE this weekend/Monday

Hi Valgrind Users and Developers! It is December already and we would really like to collect some more proposals for our FOSDEM collaboration room in Brussels on Sunday 31 January 2015. The original Call For Participation (see below) said the Talk/Discussion Submission deadline was today,

[Valgrind-users] FOSDEM Valgrind dev-room - Brussels, 31 Jan 2015

Hi Valgrind Users and Developers! It is December already and we would really like to collect some more proposals for our FOSDEM collaboration room in Brussels on Sunday 31 January 2015. The original Call For Participation (see below) said the Talk/Discussion Submission deadline was today, but we

Re: [Valgrind-users] where to find not-quite-current tarballs

On Thu, 2014-09-18 at 15:10 +0200, Mark Abraham wrote: Hi John, Thanks, I found a previously-used 3.9.0 tarball on one of my own machines. Still, a list of links on the main valgrind homepage would be a nice convenience. Yeah, looks like we have to update the archive page. Some of the old

Re: [Valgrind-users] Possible bug in valgrind?

On Wed, 2014-09-10 at 12:27 +0200, Tobias Widlund wrote: Thanks for the reply, I did download and build the valgrind version you linked and the illegal instruction error went away, but instead I am getting a segfault on the same place, as seen: OK, that is somewhat expected. valgrind

[Valgrind-users] Valgrind @ FOSDEM talk slides

Hi all, Thanks for all you who came to Valgrind devroom at FOSDEM. I think the interest in the talks surprised us all. We had to turn away some people at some talks because the room was just full. For those who missed it most slides are attached to the talk pages listed at:

[Valgrind-users] Valgrind @ FOSDEM - Sunday 2 February, 2014

and GDB integration Tom Tromey 16:00 16:25 BoF: Ideas, new features and directions for Valgrind Mark Wielaard 16:30 17:45 More background information about the talks can be found at: https://fosdem.org/2014/schedule/track/valgrind/ For the last session we are still looking for ideas to discuss

Re: [Valgrind-users] [Valgrind-developers] Valgrind @ FOSDEM - Sunday 2 February, 2014

On Mon, 2014-01-13 at 16:04 +0100, Mark Wielaard wrote: Hi Valgrind hackers, developers and users, Valgrind will have a devroom at FOSDEM 2014 on Sunday 2 February with the follow talks: Apologies for messing up the formatting. Here it is again, hopefully better readable. If not, please just

Re: [Valgrind-users] Unrecognised instruction

On Tue, 2013-11-26 at 09:36 +0100, Mark Wielaard wrote: Basically the problem (on the valgrind side) is that there is one instruction (xabort) that valgrind doesn't know about. Valgrind emulates all instructions, so when it encounters one it doesn't know about it just cannot proceed

Re: [Valgrind-users] Unrecognised instruction

On Tue, 2013-11-26 at 09:25 +0100, Joël Krähemann wrote: Am Dienstag, den 26.11.2013, 00:18 +0100 schrieb Mark Wielaard: On Mon, Nov 25, 2013 at 10:40:40PM +, Tom Hughes wrote: On 25/11/13 22:06, Joël Krähemann wrote: Hi, I get this nice error message out of valgrind while

  1   2   >