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 this both with debuginfo packages installed (using a long
list of debuginfo packages helpfully provided by gdb when debuginfod
support is declined), and with no debuginfo packages installed and
relying entirely on debuginfod to fetch debug info. I'm sure that
fetching is working at least in part, because I can remove
~/.cache/debuginfod_client completely, and it will be repopulated by a
subsequent run of valgrind.
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 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 0x14BA7DFC: ???
==29692== by 0x14B86D88: ???
==29692== by 0x146ED193: ???
==29692== by 0x1475E205: ???
==29692== by 0x1475E71A: ???
==29692== by 0x1475ED49: ???
==29692== by 0x146EF09F: ???
==29692== by 0x4A5D0E7: g_type_create_instance (gtype.c:1931)
==29692== by 0x4A42C1F: g_object_new_internal (gobject.c:2228)
==29692== by 0x4A44247: g_object_new_with_properties (gobject.c:2391)
==29692== by 0x4A44FF0: g_object_new (gobject.c:2037)
==29692== by 0x146F5395: ???
==29692== by 0x145D820C: ???
==29692== by 0x145E06E3: ???
==29692== by 0x1276D0: pk_backend_load (pk-backend.c:569)
==29692== by 0x135D1A: pk_engine_load_backend (pk-engine.c:967)
==29692== by 0x119468: main (pk-main.c:219)
==29692== 158,863 (8,192 direct, 150,671 indirect) bytes in 1 blocks are
definitely lost in loss record 2,602 of 2,602
==29692== at 0x48486AF: realloc (vg_replace_malloc.c:1451)
==29692== by 0x14805D7B: ???
==29692== by 0x148062D6: ???
==29692== by 0x1480DA3F: ???
==29692== by 0x1480FCAB: ???
==29692== by 0x14B86DF5: ???
==29692== by 0x146ED193: ???
==29692== by 0x1475E205: ???
==29692== by 0x1475E71A: ???
==29692== by 0x1475ED49: ???
==29692== by 0x146EF09F: ???
==29692== by 0x4A5D0E7: g_type_create_instance (gtype.c:1931)
==29692== by 0x4A42C1F: g_object_new_internal (gobject.c:2228)
==29692== by 0x4A44247: g_object_new_with_properties (gobject.c:2391)
==29692== by 0x4A44FF0: g_object_new (gobject.c:2037)
==29692== by 0x146F5395: ???
==29692== by 0x145D820C: ???
==29692== by 0x145E06E3: ???
==29692== by 0x1276D0: pk_backend_load (pk-backend.c:569)
==29692== by 0x135D1A: pk_engine_load_backend (pk-engine.c:967)
==29692== by 0x119468: main (pk-main.c:219)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
