A FTBFS on s390x I'd like some advices for

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Following the mass rebuild, the package utox stopped building on s390x.
The following test is failing, with a message regarding a memory leak:


+ /usr/bin/ctest --output-on-failure --force-new-ctest-process -j3
Test project /builddir/build/BUILD/uTox-0.18.1/redhat-linux-build
    Start 1: test_chatlog
    Start 2: test_chrono
1/2 Test #1: test_chatlog .....................   Passed    0.01 sec
2/2 Test #2: test_chrono ......................***Failed    0.15 sec
Running suite(s): Chrono
=================================================================
==2406587==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 24 byte(s) in 1 object(s) allocated from:
    #0 0x3ff9e73034d in __interceptor_malloc (/lib64/libasan.so.6+0xb034d)
    #1 0x3ff9e584945 in emalloc (/lib64/libcheck.so.0+0x4945)
Indirect leak of 8 byte(s) in 1 object(s) allocated from:
    #0 0x3ff9e73034d in __interceptor_malloc (/lib64/libasan.so.6+0xb034d)
    #1 0x3ff9e584945 in emalloc (/lib64/libcheck.so.0+0x4945)
SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s).
=================================================================
==2406590==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 24 byte(s) in 1 object(s) allocated from:
    #0 0x3ff9e73034d in __interceptor_malloc (/lib64/libasan.so.6+0xb034d)
    #1 0x3ff9e584945 in emalloc (/lib64/libcheck.so.0+0x4945)
Indirect leak of 8 byte(s) in 1 object(s) allocated from:
    #0 0x3ff9e73034d in __interceptor_malloc (/lib64/libasan.so.6+0xb034d)
    #1 0x3ff9e584945 in emalloc (/lib64/libcheck.so.0+0x4945)
SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s).
0%: Checks: 2, Failures: 0, Errors: 2

What I am not sure about is if the problem comes from utox itself, or if this
is an issue with libcheck or libasan?
Can someone provide me with some input?

Thanks,

Robert-André
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux