OK, I think I finally found it. There are some dummy loggers in the run
time that I added because some of the unit tests run without a fully
initialized run time (which provides access to the logger), but still
need a working logger. For these tests, a global dummy instance is used.
It's the clean-up of the dummy instance that causes the problem because,
depending on global destructor ordering, the instance may have been
destroyed at the time the atexit handler tries to finalize it.
Not sure what the best fix is yet. Working on it...
** Changed in: unity-scopes-api (Ubuntu)
Status: Invalid => In Progress
** Changed in: libqtelegram (Ubuntu)
Status: Triaged => Invalid
** Changed in: canonical-devices-system-image
Assignee: Yuan-Chen Cheng (ycheng-twn) => Michi Henning (michihenning)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472755
Title:
corrupted double-linked list probably cause by telegram scope
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1472755/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
