touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #64565
[Bug 1435186] Re: valgrind on armhf fails with with many errors
** Branch linked: lp:~afrantzis/mir/workaround-valgrind-with-glibc-2.21
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1435186
Title:
valgrind on armhf fails with with many errors
Status in Mir:
In Progress
Status in mir package in Ubuntu:
New
Bug description:
Valgrind is now failing on armhf. Both in CI and when tested manually.
This is the first and most obvious error, but there are more...
[ RUN ] UdevWrapperDeathTest.DereferencingEndReturnsInvalidObject
==10542== Invalid write of size 4
==10542== at 0x4ECA00C: ??? (in /lib/arm-linux-gnueabihf/libc-2.21.so)
==10542== Address 0xbdbafa88 is on thread 1's stack
==10542== 16 bytes below stack pointer
==10542==
==10542== Conditional jump or move depends on uninitialised value(s)
==10542== at 0x4ECA118: __udivmoddi4 (in /lib/arm-linux-gnueabihf/libc-2.21.so)
==10542==
==10542== Use of uninitialised value of size 4
==10542== at 0x4ECA11A: __udivmoddi4 (in /lib/arm-linux-gnueabihf/libc-2.21.so)
==10542==
==10542== Use of uninitialised value of size 4
==10542== at 0x4ECA018: ??? (in /lib/arm-linux-gnueabihf/libc-2.21.so)
==10542==
==10611==
==10611== Process terminating with default action of signal 11 (SIGSEGV)
==10611== Bad permissions for mapped region at address 0x2CDA000
==10611== at 0x2CDA000: ??? (in /home/phablet/mir/dev/bin/.mir_unit_tests-uninstalled)
==10611==
==10611== HEAP SUMMARY:
==10611== in use at exit: 392,022 bytes in 7,695 blocks
==10611== total heap usage: 19,288 allocs, 11,593 frees, 1,117,616 bytes allocated
==10611==
==10611== LEAK SUMMARY:
==10611== definitely lost: 0 bytes in 0 blocks
==10611== indirectly lost: 0 bytes in 0 blocks
==10611== possibly lost: 137,447 bytes in 3,483 blocks
==10611== still reachable: 254,507 bytes in 4,211 blocks
==10611== suppressed: 0 bytes in 0 blocks
==10611== Reachable blocks (those to which a pointer was found) are not shown.
==10611== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==10611==
==10611== For counts of detected and suppressed errors, rerun with: -v
==10611== Use --track-origins=yes to see where uninitialised values come from
==10611== ERROR SUMMARY: 55 errors from 4 contexts (suppressed: 6 from 6)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1435186/+subscriptions
References