touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

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.

** Also affects: libqtelegram (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: libqtelegram (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1472755

Title:
  /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***

Status in Canonical System Image:
  Confirmed
Status in libqtelegram package in Ubuntu:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1472755/+subscriptions