unity-api-bugs team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

Unfortunately, apport-retrace thinks that all three of these crash
reports have corrupt cores and don't provide useful backtraces. All of
them show that /something/ called abort(), but the retrace fails before
we get to the caller:

SourcePackage: indicator-location
Stacktrace:
 #0  0xb6b258e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #1  0xb6b3405e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #2  0xb6b34d4e in abort () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #3  0xb6c622b4 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 No symbol table info available.
 #4  0xb6c60af0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)


Same for all three traces.

FWIW there's no direct call to abort(), assert(), g_error() in the
indicator-location codebase, so the abort() call is coming from
somewhere else in the stack.

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Location.
https://bugs.launchpad.net/bugs/1338610

Title:
  indicator-location crashing during default, sdk and click_image_tests
  tests on smoketesting

Status in Indicator Location:
  New

Bug description:
  Since image #113 we have noticed crashfiles from indicator-location
  happening for 3 test suites in smoketesting: default, sdk and
  click_image_tests. Those are the non-autopilot test suites. Links to
  the crashes:

  http://ci.ubuntu.com/smokeng/utopic/touch/mako/116:20140707:20140625/8902/click_image_tests/
  http://ci.ubuntu.com/smokeng/utopic/touch/mako/116:20140707:20140625/8902/sdk/
  http://ci.ubuntu.com/smokeng/utopic/touch/mako/116:20140707:20140625/8902/default/

  Those crashers do not affect the test results, nor do they appear
  during normal usage of the phone.b

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-location/+bug/1338610/+subscriptions