Ubuntu
unity-scope-mediascanner package

  1. Bug #1472755
  2. Comment #6

Comment 6 for bug 1472755

Revision history for this message
Michi Henning (michihenning) wrote : Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted double-linked list: ADDR ***

The stack trace indicates that the crash happens after main() completes, when global objects are destroy via at_exit().
The crash happens inside the destructor for boost::log::core. (Boost log uses a global singleton instance.) However, I suspect that this is co-incidental. Most likely, memory has been corrupted.

Unfortunately, valgrind does not work for arm:

$ valgrind /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner
...
disInstr(arm): unhandled instruction: 0xEC510F1E
                 cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE)
==27306== valgrind: Unrecognised instruction at address 0x57f4ec8.
==27306== at 0x57F4EC8: ??? (in /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0)

I've run a bunch of scopes on the desktop using valgrind on the scoperunner (and therefore the scopes). It reports no errors or leaked memory.

I strongly suspect that a bug in the scope itself is responsible. If anyone can find a way to reproduce this problem, that would be immensely useful. Running the telegram scope under valgrind might yield some clues.