It's also interesting that a bit before the GLibMainLoop test failures we get some memory errors in other tests. Perhaps the stack has been corrupted?
8: [ RUN ] GMock.return_by_move 8: ==10949== Invalid write of size 4 8: ==10949== at 0x4D7AC06: ??? (in /lib/arm-linux-gnueabihf/libgcc_s.so.1) 8: ==10949== Address 0xbdb8c740 is on thread 1's stack 8: ==10949== 16 bytes below stack pointer 8: ==10949== 8: [ OK ] GMock.return_by_move (431 ms) 8: [----------] 1 test from GMock (496 ms total)
8: [ RUN ] RecursiveReadWriteMutex.can_be_read_locked_on_multiple_threads 8: ==10949== Thread 2: 8: ==10949== Invalid write of size 4
It's also interesting that a bit before the GLibMainLoop test failures we get some memory errors in other tests. Perhaps the stack has been corrupted?
8: [ RUN ] GMock.return_ by_move linux-gnueabihf /libgcc_ s.so.1) by_move (431 ms)
8: ==10949== Invalid write of size 4
8: ==10949== at 0x4D7AC06: ??? (in /lib/arm-
8: ==10949== Address 0xbdb8c740 is on thread 1's stack
8: ==10949== 16 bytes below stack pointer
8: ==10949==
8: [ OK ] GMock.return_
8: [----------] 1 test from GMock (496 ms total)
8: [ RUN ] RecursiveReadWr iteMutex. can_be_ read_locked_ on_multiple_ threads
8: ==10949== Thread 2:
8: ==10949== Invalid write of size 4