#valgrind

[just-my-insufferable-existance]

Thinking about making a post, or a series about stuff that I wish I was taught about C in school.

I might just do it regardless of interest, it would be nice to just get my thoughts written down somewhere.

Also feel free to give me some topic suggestions, like bitwise operations, memory management, object oriented-ness, fun with undefined behaviors, advanced(?) topics, etc...

[onlyhurtforaminute]

VALGRIND-OBSCURE THE SUN

[grembly]

valgrindr

[mk-average]

Sigma valgrindset

[nephriteknight]

in google docs, if you delete text with a comment it doesn't actually go away or even get marked as resolved, it just stays in the comments forever, and after agonizing over memory leaks in my code all week doing that feels like a problem somehow

[canary-song]

the epic highs and lows of coding with C

[gnomewithalaptop]

WOOT WOOT GUESS WHO JUST FIXED THEIR SHIT AND GOT IT RUNNING

This final project is worth 40% of our final grade and the other half of my team just told me they haven't even STARTED working on one of the core functionalities. What the fuck.

[cups-official]

she valgrind on my stack till I leak

[studentbyday]

day 21-23 // 100doc && day 33-38 // 100dop

sunday: i finished filter less but it seems a waste of a post to just post that so i'm compiling several days into one post (also hopefully this way i'll spend less time on social media lol edit: idk how well that worked...😅).

monday: read + studied some chemistry

tuesday: more chemistry (didn't get to finish all the chapters for this week ofc 🙄)

wednesday: finished 1st chem chapter. halfway through the 2nd.

thursday: slowly getting through the 2nd half of the last chem chapter for this week. finally got recover to return actual images. but valgrind is still throwing errors so gotta fix that...

friday: fixed valgrind errors. 1 and 1/2 sections of the chem chapter left to go and then i'm done with the readings. i hope i'll be able to finish them tmr as well as the quiz and lab report AND start that data structures lecture... 😬

saturday: finished chem chapter, quiz, and started lab report

[ctrl-salt-delete]

The malicious changes were submitted by JiaT75, one of the two main xz Utils developers with years of contributions to the project. “Given the activity over several weeks, the committer is either directly involved or there was some quite severe compromise of their system,” Freund wrote. “Unfortunately the latter looks like the less likely explanation, given they communicated on various lists about the ‘fixes’” provided in recent updates. Those updates and fixes can be found here, here, here, and here. On Thursday, someone using the developer's name took to a developer site for Ubuntu to ask that the backdoored version 5.6.1 be incorporated into production versions because it fixed bugs that caused a tool known as Valgrind to malfunction. “This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass,” the person warned, from an account that was created the same day. One of maintainers for Fedora said Friday that the same developer approached them in recent weeks to ask that Fedora 40, a beta release, incorporate one of the backdoored utility versions. “We even worked with him to fix the valgrind issue (which it turns out now was caused by the backdoor he had added),” the Ubuntu maintainer said. "He has been part of the xz project for two years, adding all sorts of binary test files, and with this level of sophistication, we would be suspicious of even older versions of xz until proven otherwise." Maintainers for xz Utils didn’t immediately respond to emails asking questions.

[just-my-insufferable-existance]

I've started streaming!

I'm still working on establishing myself and "brand", but I'm considering doing programming streams.

More info might follow.

[onlyhurtforaminute]

VALGRIND-MILLENIUM OF NIGHT BLISS

[taohun]

lmao look what valgrind said about the code i was given to debug

[tjsomething]

This part's kind of ripped from the headlines, when 7-Zip got ported to XZ Utils. It got backdoored by a Chinese spy who took advantage of the original dev's mental health issues to get control of the project as part of a 5 year long con. The spy was only caught because a Postgres dev noticed high CPU usage from XZ after getting Valgrind errors a couple weeks before.

[codingprolab]

CS61C Lab 2 - Advanced C and Memory Management

Goals Look at the internal representation of numbers. Practice working with dynamic memory allocation. Introduce you to Valgrind, a utility for checking memory leaks. Setup Copy the contents of ~cs61c/labs/02 to a suitable location in your home directory. You do not need to add the lab files to your git repo. $ cp -r ~cs61c/labs/02/ ~/labs/02 Exercise 1: Bit Operations For this exercise, you will…

[codezup]

Mastering Memory Management in C++: Valgrind and AddressSanitizer