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

On 12/10/2023 08:53, Paul Floyd wrote: 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

Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors

That depends how you define support. I use it on a Ryzen all the time, but not with code compiled to target all the AMD specific extensions, which we do not currently have support for. Tom On 19/07/2023 12:39, Stuart Foster via Valgrind-users wrote: I am trying to find which of my systems will

Re: [Valgrind-users] valgrind gets fatal signal when particular syscall is made by an executable

On 03/07/2023 10:42, Daniel Fishman wrote: Thanks for the pointer. I just commented out the line for the mentioned syscall number from valgrind's syscall table, and this workaround was enough to solve the problem. Since the custom syscall doesn't modify its parameters and doesn't seem to write a

Re: [Valgrind-users] Valgrind not finding issue with writing/reading past array?

This is in fact documented in the FAQ here: https://valgrind.org/docs/manual/faq.html#faq.overruns The fact it's an array is not actually important - there is no overrun detection for any global or stack variables. The reason is that because valgrind is operating on an existing binary there is

Re: [Valgrind-users] memcheck is getting SIGKILLed before leak report is output

On 01/09/2022 01:03, Bresalier, Rob (Nokia - US/Murray Hill) wrote: Don't understand why strace log has exit(0) without the underscore, I know for a fact that it was with the underscore. Because exit() and _exit() are C library functions but both call the SYS_exit system call and that is what

Re: [Valgrind-users] memcheck is getting SIGKILLed before leak report is output

On 05/08/2022 14:09, Bresalier, Rob (Nokia - US/Murray Hill) wrote: When running memcheck on a massive monolith embedded executable (237MB stripped, 1.8GiB unstripped), after I stop the executable under valgrind I see the “HEAP SUMMARY” but then valgrind dies before any leak reports are printe

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

1, 2022 4:56 AM To: Tom Hughes ; Mark Roberts ; valgrind-users@lists.sourceforge.net Subject: Re: [Valgrind-users] new error message from Valgrind On Thu, 2022-07-28 at 22:22 +0100, Tom Hughes via Valgrind-users wrote: On 28/07/2022 21:39, Mark Roberts wrote: I recently upgraded from Ubutu 20.0

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

On 28/07/2022 21:39, Mark Roberts wrote: I recently upgraded from Ubutu 20.04 to 22.04 and am now getting a new error message from Valgrind: --915-- WARNING: unhandled amd64-linux syscall: 334 --915-- You may be able to write your own handler. --915-- Read the file README_MISSING_SYSCALL_OR_I

Re: [Valgrind-users] armhf: illegal hardware instruction

On 29/06/2022 15:49, Mathieu Malaterre wrote: Here is what I get on first try: Program received signal SIGILL, Illegal instruction. vgPlain_am_startup (sp_at_startup=3204445696) at m_aspacemgr/aspacemgr-linux.c:1626 1626 init_nsegment(&seg); (gdb) x/i $pc => 0x58071090 : vmov.i32

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

On 26/06/2022 09:13, ellie wrote: How do I run openssl programs in valgrind on processors where it causes SIGILL? https://www.openssl.org/docs/faq.html#PROG17 In what way is it not working? When valgrind encounters an instruction it doesn't understand it logs the details and then passes the S

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

On 20/04/2022 13:41, Tom Hughes via Valgrind-users wrote: Again until we know what "AMX features" are it's impossible to comment in any detail. So apparently AMX is this: https://en.wikipedia.org/wiki/Advanced_Matrix_Extensions So not only is it new instructions, it is new

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

On 20/04/2022 13:18, Yang Zhong wrote: On Wed, Apr 20, 2022 at 09:37:17AM +0100, Tom Hughes wrote: On 20/04/2022 09:01, Yang Zhong wrote: So, from above issue in Intel new platform, the valgrind need do some enablings to be compatible with on new platform? Seems valgrind tool can't identify t

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

On 20/04/2022 09:01, Yang Zhong wrote: So, from above issue in Intel new platform, the valgrind need do some enablings to be compatible with on new platform? Seems valgrind tool can't identify the real HW platform because cpuid can't read correct register value. thanks! When running under va

Re: [Valgrind-users] CPU simulation and instruction simulation

On 06/02/2021 07:59, Muhui Jiang wrote: I am new to Valgrind and have some questions about the principles of Valgrind. According to the manual, https://valgrind.org/docs/manual/manual-core.html#manual-core.whatdoes "Yo

Re: [Valgrind-users] using valgrind to debug uninitialized mem in servern

On 04/02/2021 10:57, Matthias Apitz wrote: El día jueves, febrero 04, 2021 a las 09:48:23a. m. +, Tom Hughes escribió: On 04/02/2021 09:26, Matthias Apitz wrote: At the moment we use the following "trick": the librarian runs in parallel to the client on the desktop a second window with a

Re: [Valgrind-users] using valgrind to debug uninitialized mem in servern

On 04/02/2021 09:26, Matthias Apitz wrote: At the moment we use the following "trick": the librarian runs in parallel to the client on the desktop a second window with a "tail -f ..." on valgrinds log file (STDOUT) and the full screen is recorded with Microsoft teams functionality. So we can use

Re: [Valgrind-users] printing the values of arguments for strcpy(3), memmove(3), ...

On 26/01/2021 09:32, Matthias Apitz wrote: So far so good. What would have helped me is that vg could print in its replacement functions for memmove(3) ... (vg_replace_strmem.c:1270) the provided pointers and other args, and as well part of the src buffer. For sure vg knows exactly these values

Re: [Valgrind-users] [Need Help] Valgrind on Cavium-Octeon-3

No idea - that will be down to your cross build toolchain. Tom On 10/01/2021 18:21, mihir amrelia wrote: Tom, Thanks a lot for your response. Yes, it doesn't look like the one I should be expecting.. file /var/tmp/cavium/bin/valgrind /var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MI

Re: [Valgrind-users] Integrating Valgrind into code

On 07/01/2021 19:15, Aaron Boxer wrote: I am hunting for an uninitialized memory issue. I have integrated valgrind into my code, using cmake find_package, but when I call |VALGRIND_CHECK_MEM_IS_DEFINED| it always returns 0 no matter what I pass in. For example |VALGRIND_CHECK_MEM_IS_DEFINED(0x

Re: [Valgrind-users] [Need Help] Valgrind on Cavium-Octeon-3

On 07/01/2021 10:54, mihir amrelia via Valgrind-users wrote: I am trying to get valgrind running on cavium octeon 3 processor. Couldn't find any specific build configs for this other than some hints on the valgrind wiki. * * * The steps executed to build valgrind for cavium were (on x86_64 h

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

That's correct as AVX512 is not currently supported in valgrind so you will need a version that doesn't use that for valgrind use. Progress on adding AVX512 support is being tracked here: https://bugs.kde.org/show_bug.cgi?id=383010 Tom On 26/05/2020 10:07, Patrick Bégou wrote: Thanks all for

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

Sorry, I misunderstood what you meant by "as previous version" there. I thought you meant the previous version worked but you actually meant that it failed. As Julian says there is no easy fix - you have a library installed that has been compiled to assume certain instructions are available that

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

On 26/05/2020 09:06, Patrick Bégou wrote: valgrind-3.16.0.RC2 doesn't work for me (as previous version on this server). Are you saying that it fails on a binary that worked before? vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x8 0x6F 0x5 0x25 0xA8 0x18 0x0 vex amd64->IR:   RE

Re: [Valgrind-users] Program crashes with valgrind

On 20/05/2020 17:01, James Read wrote: On Wed, May 20, 2020 at 2:31 PM Tom Hughes > wrote: On 20/05/2020 14:23, James Read wrote: > I'm trying to use valgrind to track down a memory leak in my web > crawling application. The problem is my application run

Re: [Valgrind-users] Program crashes with valgrind

On 20/05/2020 14:23, James Read wrote: I'm trying to use valgrind to track down a memory leak in my web crawling application. The problem is my application runs just fine without valgrind but when I run it under valgrind the program crashes before it has a chance to crawl any websites. Any ide

Re: [Valgrind-users] New user and first problem

On 18/05/2020 18:48, Julian Seward wrote: Program received signal SIGILL: Illegal instruction. Backtrace for this error: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x8 0x6F 0x5 0x25 0xA8 0x18 0x0 vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR:   VEX=0 VEX.

Re: [Valgrind-users] Write new tool in C++?

On 04/03/2020 14:46, Derrick McKee wrote: Is it possible to write a tool using C++ instead of just C? In theory, maybe, but the problem you're going to have is that you have no run time library support - no libstdc+++ and not even any libc. So there are probably various things that need run ti