On 2023-01-16 05:24, Kalev Lember wrote:
On Mon, Jan 16, 2023 at 2:21 PM Richard W.M. Jones
wrote:
Also make use of suppressions:
https://gitlab.com/nbdkit/nbdkit/-/tree/master/valgrind
Also, to add to this, glib2 has a suppressions file you can use to cut
down on the false
On 2023-01-16 01:38, Tom Hughes wrote:
I suspect this is a result of libraries being opened and closed
dynamically...
Try using --keep-debuginfo=yes to make valgrind cache debuginfo
for libraries that have been closed.
Yes, that was it. I did not know this about valgrind. Thank you!
I'll
On Mon, Jan 16, 2023 at 2:21 PM Richard W.M. Jones
wrote:
> Also want to mention that your valgrind command line is ... a little
> naive. Many other options are useful. Here's what we use in nbdkit:
>
>
>
On Mon, Jan 16, 2023 at 12:52:38AM -0800, Gordon Messmer wrote:
> ==29692== 30 bytes in 2 blocks are definitely lost in loss record
> 917 of 2,602
> ==29692== at 0x484386F: malloc (vg_replace_malloc.c:393)
> ==29692== by 0x14806539: ???
> ==29692== by 0x14BA7D87: ???
> ==29692== by
On Sun, Jan 15, 2023 at 10:10:24PM -0800, Gordon Messmer wrote:
> I'm working on reducing memory use in packagekitd, and so far
> progress has been very good. I've opened 4 memory-related PRs
> against PackageKit and libdnf this week, and locally I've reduced
> memory use at idle by almost 90% (I
On 16/01/2023 08:52, Gordon Messmer wrote:
On 2023-01-16 00:31, Tom Hughes via devel wrote:
If that doesn't work then some examples would help, at least if you're
getting a partial trace, so that we can get some idea of what component
it is not able to unwind.
==29692== 30 bytes in 2
On 2023-01-16 00:31, Tom Hughes via devel wrote:
On 16/01/2023 08:12, Florian Festi wrote:
Have you installed the debuginfo packages for the packages involved?
See man debuginfo-install
Making sure debuginfod fetching works should also do it as valgrind
has support for that.
I've tried
On 16/01/2023 08:12, Florian Festi wrote:
On 1/16/23 07:10, Gordon Messmer wrote:
Does anyone have any hints for improving the information I get from
valgrind?
Have you installed the debuginfo packages for the packages involved?
See man debuginfo-install
Making sure debuginfod fetching works
On 1/16/23 07:10, Gordon Messmer wrote:
> Does anyone have any hints for improving the information I get from
> valgrind?
Have you installed the debuginfo packages for the packages involved?
See man debuginfo-install
Florian
___
devel mailing list --
I'm working on reducing memory use in packagekitd, and so far progress
has been very good. I've opened 4 memory-related PRs against PackageKit
and libdnf this week, and locally I've reduced memory use at idle by
almost 90% (I can reliably cause stock packagekitd to use ~ 700MB of RAM
in a
On Thu, 06 Dec 2018 11:59:35 +0100, Germano Massullo wrote:
> This seems to not happen with Valgrind
I would first suggest using compiler option -fsanitize=address instead of
valgrind.
Jan Kratochvil
___
devel mailing list --
I have to debug certain BOINC Manager problems (C++ language), and
instead of importing and building the whole source tree in a project
in a SDK like Eclipse, I want to simply use the debuginfos already
available in Fedora repository.
Concerning GDB usage I can do that with QtCreator. It attaches
12 matches
Mail list logo
