paulf38

9 ms·

1.
by paulf38 3mo ago
Is that something that should be merged to upstream Valgrind?
2.
by paulf38 4mo ago
And sadly that was one that I broke trying to refactor together all our C++ autoconf tests. Silver lining, I added a test for it so if I break it again we should notice earlier.
3.
by paulf38 4mo ago
"some community effort" is a huge understatement. Let me rephrase that for you: "Possibly the largest ever single contribution to Valgrind". Initial work on this was started by an engineer at Intel. She was based in St P
4.
Valgrind-3.27.1 Is Available
12 points by paulf38 4mo ago|2 comments
5.
Valgrind-3.27.0 Is Available(sourceforge.net)
1 points by paulf38 5mo ago|0 comments
6.
by paulf38 5mo ago
3.27.0 RC2 is now out. An RC2 tarball for 3.27.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC2.tar.... (md5sum = 64b955764abeb80fd3e0b6287e596750) (sha1sum = a52b15d2f75619762fb1c5007
7.
by paulf38 5mo ago
For the contents, see https://sourceware.org/git/?p=valgrind.git;a=blob;f=NEWS;h=d...
8.
Valgrind 3.27 RC1 is out
2 points by paulf38 5mo ago|2 comments
9.
by paulf38 5mo ago
AI slop.
10.
by paulf38 6mo ago
We still use KDE's bugzilla. One of the reasons that Vagrind was initially developed was to help with KDE back when many developers didn't really understand how to use new and delete. These days sourceware.org hosts the Valgrind g
11.
by paulf38 7mo ago
There was someone at Intel working on AVX512 support in Valgrind. She is/was based in St Petersburg. Intel shuttered their Russian operations when Putin invaded Ukraine and that project stalled. If anyone has the time and knowledge to
12.
by paulf38 7mo ago
The problem is that there are many many people that are falling over themselves to believe bogus claims about false positives. Outside of Valgrind bugzilla bug reports these claims almost never stand up to close scrutiny. Not that the peop
13.
by paulf38 8mo ago
I'm working on Valgrind on macOS, integrating Louis Brunner's work and trying to add a few more fixes. In 2025 support for macOS Intel 10.14, 10.15 11 and 12 was added. Intel macOS 13 is a bit harder of a nut to crack. And I have
14.
by paulf38 8mo ago
If anyone can help adding AVX512 (and other CPU features) support then that would be most welcome. It’s a major task though.
15.
by paulf38 8mo ago
> even with Valgrind and similar tools, you are still going to run into weird destructor issues with inheritance. I love these folklore comments. Post an example.
16.
by paulf38 8mo ago
In my experience that is usually the result of years and years of accumulation of shit code. The results is thousands of leaks. That makes detection of incremental leaks much more difficult. If you start with clean code and use ASAN or Valg
17.
by paulf38 8mo ago
OOP is pretty much has-been. Value semantics is the hot thing now I'd say.
18.
by paulf38 9mo ago
Rather brassy claims. Your library has many issues. Some should be easy to fix. You missed many allocation/deallocation functions (3 from ISO C, 1 from POSIX and 4 non-standard ones). Others will be difficult or impossible for you to a
19.
by paulf38 10mo ago
Valgrind (and the sanitizers) are only as good as your test coverage. Static analysis can cover all your code, though generally with a significant rate of false positives that you will need to analyse.
20.
by paulf38 10mo ago
Are you trying to explain to me how Valgrind works? If you do know more than me then please join us and become a Valgrind developer. Mostly it wraps system calls and library calls. Wrapping means that it does some checking or recording befo
21.
by paulf38 10mo ago
> Valgrind is a mock of standard library/OS functions and I think its existence is a good thing. That is mostly wrong. Valgrind wraps syscalls. For the most part it just checks the arguments and records any reads or writes to memory
22.
by paulf38 10mo ago
I agree that C is a basket case when it comes to safety and security. The CPU and the hardware don’t care how confident C coders are in their ability. C developers tend to forget the reason why Windows and UNIX like systems are now quite ro
23.
by paulf38 10mo ago
I do most of the Valgrind maintenance these days.
24.
by paulf38 10mo ago
I wrote a series of articles for ACCU overload back around 2012 to 2013. This was in 6 parts. Introduction https://accu.org/journals/overload/20/108/floyd_1930/ Basic memcheck https://acc
25.
by paulf38 11mo ago
Nooooo! "valgrind memory leak". Aaargh. Valgrind (memcheck) is not just a leak detection tool. Leak detection is so unimportant that it isn't even turned on by default.
26.
by paulf38 11mo ago
In what way are the error reports "just noise"?
27.
by paulf38 11mo ago
You didn't look very hard. The person that I replied to said " Disciplined use of c, with modern tools like valgrind, will give you safe code".
28.
by paulf38 11mo ago
TBH most “false positives” that I investigate are wishful thinking or the result of ignorance of what is really happening. It looks like you are using Debian. That probably doesn’t help. Here is a typical Debian “bug” report: https:/&
29.
by paulf38 11mo ago
It would be nice (speaking as a Valgrind developer) if Valgrind could guarantee safe code. Unfortunately it doesn’t. Firstly, it does not detect all kinds of errors (and indeed no tool does). Secondly, it is unlikely that the test coverage
30.
by paulf38 11mo ago
I always assume that anyone that says that something is a false positive without providing any rigorous proof has confirmation bias and are sadly deluding themselves about their ability and the correctness of their code.

More ›