5 ms·
It only works if every package tests with it. Otherwise the relevant warnings get swamped by a huge amount by irrelevant warnings. This is why running Valgrin
by amelius 1y ago
It only works if every package tests with it.
Otherwise the relevant warnings get swamped by a huge amount by irrelevant warnings.
This is why running Valgrind on Python code does not work.
- jzwinck 1y agoIf that were true it would also apply to C and C++. I have used Valgrind with Python + Boost C++ hybrid programs and it worked fine after spending an hour making a suppressions file.
- giancarlostoro 1y ago> it worked fine after spending an hour making a suppressions file. So you are confirming the problem, but treating it as if ignoring it is the solution for all?
- sauercrowd 1y agoit's a rejection of the thesis that it "does not work". It does, but it requires investing into a suppression file.
- amelius 1y agoYeah I tried that on a PySide6 application. Trust me, it does not work.
- fragmede 1y agoskill issue
- hu3 1y agoplus, LLMs can generate suppressor files from logs. It's much faster these days. I've had success with this approach.
- gizmo686 1y agoValgrind can generate suppression files directly.
- hu3 1y agoyes but LLMs have access and understanding of my code and can better discern what should be suppressed.
- skissane 1y agoYes, but in my past experience, one often wants to be edit those files to make them more generic… Valgrind struggles to distinguish which parts of the call stack are essential to a “known leak” versus which are coincidental. I have never tried asking an LLM to do this-but it seems like the kind of problem with which an LLM might have some success, even if only partial success.
- EasyMark 1y agoIs an hour a big deal if it's something you can use over and over and over for debug purposes going forward?
- ahartmetz 1y agoFor me, a waaay outdated suppressions file for Qt + a rough understanding what syscalls and frameworks do is enough. If my app crashes in a network request and a byte sent to the X server (old example, I use Wayland now) is uninitialized, I know to ignore it. Valgrind(-memcheck) is an extremely important tool in memory-unsafe languages.
- esbranson 1y agoSimplification of overwhelming information sounds like a good use case for local LLMs. So I agree with other comments that toolchains are better positioned to include batteries like Valgrind.
- Thaxll 1y agoWhat do you mean if every package tests with it in the context of Go?