Valgrind Reviews and Details

Is Valgrind good?

Social recommendations and mentions

• Why does Debian change software?

  Hello, as always: imho (!) I remember this incident - if my memory doesn't trick me: it was openssl which accessed memory it didn't allocated to collect randomness / entropy for key-generation. And valgrind complained about a possible memory-leak - its a profiling-tool with the focus on detecting memory-mgmt problems. * https://valgrind.org/ instead of taking a closer look / trying to understand what exactly went... - Source: Hacker News / about 2 months ago

• Understanding the Odin Programming Language

  Odin has a builtin heap allocator that works the same way you would expect any other high-level language to do memory allocation–it's just that you have to free the memory yourself. Plus, Odin's built in `context` system makes it really easy to change what kind of allocator is used for different sections of code. For my use cases, I've never needed any more than a heap and an arena, detailed in this talk:... - Source: Hacker News / 7 months ago

• Intel Announces Retirement of CEO Pat Gelsinger

  Dunno, who says a lot of effort was put into Rosetta 2? It's mostly something that was needed in the first few years so you could run Chrome and Photoshop, but those have been ported now. It's mostly useful for running WINE but that's not super common outside games. That said, a binary recompiler has a lot of uses once you have one: https://valgrind.org. - Source: Hacker News / 8 months ago

• Top 10 Profiler Tools for Optimizing Software Performance in 2024

  Valgrind is an open-source profiling tool suite ideal for debugging and profiling C and C++ applications. - Source: dev.to / 8 months ago

• Use Valgrind in your CI / CD

  Today I will show you how to use Valgrind to easily check for memory leaks on your code inside a GitHub Action. - Source: dev.to / about 1 year ago

• Memory Safe or Bust?

  Continuous Integration and Continuous Deployment [CI/CD] pipelines play a crucial role in enforcing code quality, especially when working with memory-unsafe languages. By integrating automated dynamic analysis tools like Valgrind or AddressSanitizer, static analysis tools like Clang Static Analyzer or cppcheck, and manual code review processes, developers can identify and mitigate many memory-related... - Source: dev.to / over 1 year ago

• Top 7 C++ Tools to explore in 2024 if it's not already the case.

  Valgrind is an open-source tool designed to help developers identify memory management issues, memory leaks, and various other types of memory-related errors in their programs. It's commonly used for debugging and profiling purposes, particularly in C and C++ development. Here's an overview of Valgrind:. - Source: dev.to / over 1 year ago

• Debugging OpenGL with GDB causes shader issues

  Valgrind is a tool for debugging memory errors. We have it installed on our linux machines at work. I'm not sure how difficult this is to install and setup. You can find more info here: https://valgrind.org/. Source: over 1 year ago

• Ask HN: Good practices for my first C project

  It's often best not to think too much about "aesthetic", or performance, at first, and to focus instead on getting something that works, correctly. FWIW, The Mythical Man-Month[0] recommends to start with a few throw-away prototypes, during which you're gaining expertise over the problem, that you can later crystallize in more definite versions. Now, it doesn't mean good practices should be discarded... - Source: Hacker News / over 1 year ago

• C++ is everywhere, but noone really talks about it. What are people's thoughts?

  I think you're on the right path, yes. Usually I use Valgrind for all memory related debugging, not sure if it can help you here. Source: about 2 years ago

• Is malloc_trim() safe to use?

  Have you tried using tools like ASAN/LSAN or valgrind to confirm that there are indeed no memory leaks? Source: about 2 years ago

• Testing Vlang, Rust and Zig and more!

  Tested my silly app with Valgrind and for few minutes run I had around 2 MB of memory leak. - Source: dev.to / about 2 years ago

• Autodiff in C (need help fixing memory leak)

  I would recommend having a look at Valgrind: https://valgrind.org/. Source: over 2 years ago

• Why So Slow? Using Profilers to Pinpoint the Reasons of Performance Degradation

  First, we used Callgrind to get some results. Using Callgrind massively slowed down the execution. In some cases, it was almost 20 times slower than the unprofiled version. Callgrind is based on Valgrind, which uses dynamic binary instrumentation to inspect and control different aspects of applications, causing a significant slowdown. We used KCachegrind to interpret and visualize the reports generated by... - Source: dev.to / over 2 years ago

• trouble fixing memory leak in C..

  If you post your actual code, somebody might be able to help you spot the problem. You could also try running your program under a memory checker like Valgrind. Or you could just add debug logs with the addresses of the objects that you're allocating/freeing, so that you can track down where they don't match up. Source: over 2 years ago

• [C] program which lists all files in a directory recursively

  A memory checker like Valgrind can help you by automatically identifying issues like this. Source: almost 3 years ago

• Concatenating two linked lists

  In addition to a debugger, you can use a memory checker like Valgrind to more precisely narrow down the source of illegal memory accesses. Source: almost 3 years ago

• What could cause a program to not work in debug mode, but release mode works just fine?

  Since everyone else has gone into great detail, now is a good time to learn about Valgrind (specifically memcheck). It can help you find memory-based issues with your code. Source: almost 3 years ago

• From Novice to contributor to Linux Kernel and/or other Low-Level projects

  You can also use tools like Valgrind (https://valgrind.org/) or Asan (https://en.wikipedia.org/wiki/AddressSanitizer) to execute applications and look for possible leaks or other issues reported (such as invalid memory accesses and such). Source: almost 3 years ago

• Modern C++ Won't Save Us · Alex Gaynor

  But beyond std::shared_ptr, the post doesn't address modern mitigations like increasingly smarter static analysis (better compiler warnings and linting tools), runtime analysis like AddressSanitizer and Valgrind, and best practices like the C++ Core Guidelines to try to learn from the language's long history and past mistakes. These things make a big difference in making C++ a usable language. Source: about 3 years ago

• The Curious Case of the Disappearing “if”

  My next step was to try Valgrind — nothing useful. I also tried address and undefined behavior sanitizers — also nothing useful. Now what? - Source: dev.to / about 3 years ago