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 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)
I suspect this is a result of libraries being opened and closed
dynamically - for performance reasons valgrind doesn't resolve names
until it prints the trace and if the library in question has been
closed by then it will normally be unable to resolve names from it.
Try using --keep-debuginfo=yes to make valgrind cache debuginfo
for libraries that have been closed.
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
