The glibc-debug package on #artix debuginfod server hasn't been updated. glibc package is on 2.38-2, debuginfo has 2.37-3.

This breaks #valgrind.

And _why_ doesn't artix provide debug packages in their repositories? I'm very close to switching distro just because of this.

valgrind can’t detect the Cross border visits #detect #valgrind

https://askubuntu.com/q/1481436/612

The #debian #arm64 build are disabled for now because the Hardkernel ODROID-N2Plus board didn't come back up after a kernel upgrade.

https://builder.sourceware.org/buildbot

#elfutils #libabigail #dwz #bzip2 #valgrind #debugedit

Why would valgrind with `--inclusive=yes` say that a function used 30% of the time but a graph visualisation that also seems to do inclusive timing (breaking it into each child leg) only shows 2.5% of the time in the same function and the things it calls? 🤨

#Linux #debugging #DeveloperProblems #Valgrind

My first attempt to find memory leaks in #rustlang and I'm using #Valgrind for the first time.

Sensible?
#Rust #debugging

Checking usage of realloc with #Valgrind

https://developers.redhat.com/articles/2023/05/31/checking-usage-realloc-valgrind

realloc has a surprising number of tricky corner cases to watch out for. Valgrind Memcheck will help you find various issues like using it with bad arguments, pointers that might have become invalid, and leaks of blocks that have been resized.

Also, don't forget to use #GCC with -fanalyzer, -Wuse-after-free, and -Wfree-nonheap-object to catch some of these issues early.

grmpf, ein #Speicherleck.

Und #valgrind stürzt ab … #gdb hingegen sieht keine Probleme 🥴

And my next #C question 🙂

I use #popt a lot, it is great.

I always find some post issue left over when running #valgrind, caused by post. It is always small and so not something I worried much about.

I noticed it seems to be that a string argument to my command from popt is in fact malloc'd. I.e. I can free() it without error, and that fixes the valgrind complaint.

But the man page on popt does not say which things it malloc's.

Does popt always do it? What things does it do it for?

RT @gregthelaw
🆕 I just published this C++ debugging tutorial, offering a quick introduction to 2 powerful debugging tools you ought to have in your toolbox: #Valgrind and #AddressSanitizer https://hubs.ly/Q01MX6Pq0
#cplusplus #cpp #debug

I updated the #svgo #snap package to the latest last night, on stable, and the #valgrind snap to the current release candidate. That is only available on the edge channel, if you wish to test.

Sometimes contributing to open source can be easy as asking for a patch to be merged:
https://bugs.kde.org/show_bug.cgi?id=464609#c1

And sometimes this is enough for the patch to be merged:
https://sourceware.org/git/?p=valgrind.git;a=commit;h=d387566dd7dbb2ebe6fea5bfb4b2353bd5ab86ba

#valgrind #opensource

@ixn

>*Sigh*, so does #Valgrind on #Arch Linux

I initially misread that, as "Valvegrind", then began constructing mental pictures of, say, a 1970s Triumph Dolomite Sprint DOHC, partly stripped down to do a valve grind.

As you were.
Nothing to see here.
Move along.

*Sigh*, so does #Valgrind on #Arch Linux now require the always-online DRM* known as "debuginfod" to even start, *and* the glibc package must be exactly the right version?

I guess I'll have to recompile glibc… or steal it from some other distro.

* okay, maybe it isn't quite that bad… but it should not be necessary.

The #Evolvotron project has a single Python 2 script used to generate documentation. Fedora no longer provides version 2 by default, so I rewrote it in #Boron (a #Rebol inspired language) as I'm already using that to build the binary.

The new script is a bit smaller (and cleaner without all the "self" nonsense), but runs 100x faster and uses 10x less memory than Python 2.

The #valgrind measurements are in the commit message:

https://github.com/WickedSmoke/evolvotron/commit/43514c4ca254

Small is beautiful.

I was wondering why #valgrind complained about unused allocated bytes. Took a while to realize the struct field alignment left holes in the struct, which were being written into savefile. #C

@JZPrime A class I took in college and which should have free online materials, had a great lesson on debugging with #gdb and #valgrind to disarm a virtual bomb without setting it off.

I found it. https://cs61.seas.harvard.edu/site/2021/BinaryBomb/ I recommend it!

No! As usual, the reviews and IRC chats with @andriyngvason were extremely kind and valuable.

First of all, wayvncctl needed a better human-friendly pretty-printer for the json responses. Sure!

More importantly, we were using libjansson for the json library which uses a refcount system for memory management. #valgrind pointed out a number of mistakes I made on both the server and the client that required more refactoring.

Finally, it was ready: https://github.com/any1/wayvnc/pull/171

#Valgrind turned 20! 🎂 Nicholas Nethercote wrote about it:
https://nnethercote.github.io/2022/07/27/twenty-years-of-valgrind.html

I was surprised to learn Seward started as a GHC hacker.

Anyway, happy birthday, and 👍 to everyone involved!

Twenty years of Valgrind: https://nnethercote.github.io/2022/07/27/twenty-years-of-valgrind.html #linux #foss #update #valgrind #anniversary

#glibc 2.35-6 ist gestern auf dem Manjaro stable branch released worden und behebt das Problem mit #Valgrind. Der Downgrade-Workaround ist also nicht mehr nötig